headers
John Small | 17 Jan 2006 23:44

Re: No WU available message in JBSWU_Monitor

** Reply to message from "kemyers91384" <keithmyers <at> comcast.net> on Tue, 17 Jan
2006 19:26:26 -0000

>I'm getting this message currently on one of my clients. It is
>currently processing the last WU available in its cache while still
>awaiting 1 upload and 3 downloads from the servers.

I believe I have found this bug.  A complete fix for this will be uploaded
within the next day (I am in the middle of preparing the next release).  

In the meantime, a "quick and dirty" fix is to change the line:
      if (wu_queued = 0) then
to
      if (wu_queued = -1) then

See how this works for you.  It should work well as long as there is a WU being
processed.

--

-- 
John Small

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/seti-warp/

<*> To unsubscribe from this group, send an email to:
    seti-warp-unsubscribe <at> yahoogroups.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Small | 18 Jan 2006 01:03

Re: Re: Re: HOW MANY OF US ARE USING OS/2 BOINC CLIENT ?

** Reply to message from Robert Gammon <rgammon51 <at> yahoo.com> on Tue, 17 Jan
2006 13:17:41 -0600

>   One feature that will be of interest to most of us is the ability to 
>execute an Update from inside the program to get a machine to report 
>results to the servers....

Robert is a little premature about this.  It has not yet been decided that
JBSWU will include an ability to "execute an update".

JBSWU does and will have the ability to:
  1) Check periodically for new credit when it expects credit to be granted.
  2) Check for new credit in response to user action.

If the above is deemed insufficient or if there are many people who want this
feature, I will add it.  Until then, however, I am hesitant to add this feature
because:
  1) "Update" has some significant overhead (See previous messages on this list
for the earlier discussion) and I am reluctant to facilitate over-use.
  2) An update can be performed easily using boinc_cmd or with my
soon-to-be=released REXX version of boinc_cmd.  So keeing it out of JBSWU is in
no way denying users access to this operation.

--

-- 
John Small

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
(Continue reading)

Permalink | Reply | 0 comments |
headers
kemyers91384 | 18 Jan 2006 02:02
Picon

Re: No WU available message in JBSWU_Monitor

--- In seti-warp <at> yahoogroups.com, "John Small" <jsmall <at> o...> wrote:
>
> ** Reply to message from "kemyers91384" <keithmyers <at> c...> on Tue, 17 Jan
> 2006 19:26:26 -0000
> 
> 
> >I'm getting this message currently on one of my clients. It is
> >currently processing the last WU available in its cache while still
> >awaiting 1 upload and 3 downloads from the servers.
> 
> I believe I have found this bug.  A complete fix for this will be
uploaded
> within the next day (I am in the middle of preparing the next
release).  
> 
> In the meantime, a "quick and dirty" fix is to change the line:
>       if (wu_queued = 0) then
> to
>       if (wu_queued = -1) then
> 
> See how this works for you.  It should work well as long as there is
a WU being
> processed.
> 
> -- 
> John Small
>
John, I just checked the monitor about 15 minutes ago and it has
apparently fixed itself on its own and was successful in downloading 1
of 3 pending downloads and 1 of 2 pending uploads now that the servers
(Continue reading)

Permalink | Reply | 0 comments |
headers
kemyers91384 | 18 Jan 2006 02:06
Picon

Re: HOW MANY OF US ARE USING OS/2 BOINC CLIENT ?

--- In seti-warp <at> yahoogroups.com, "John Small" <jsmall <at> o...> wrote:
>
> ** Reply to message from Robert Gammon <rgammon51 <at> y...> on Tue, 17 Jan
> 2006 13:17:41 -0600
> 
> 
> >   One feature that will be of interest to most of us is the
ability to 
> >execute an Update from inside the program to get a machine to report 
> >results to the servers....
> 
> Robert is a little premature about this.  It has not yet been
decided that
> JBSWU will include an ability to "execute an update".
> 
> JBSWU does and will have the ability to:
>   1) Check periodically for new credit when it expects credit to be
granted.
>   2) Check for new credit in response to user action.
> 
> If the above is deemed insufficient or if there are many people who
want this
> feature, I will add it.  Until then, however, I am hesitant to add
this feature
> because:
>   1) "Update" has some significant overhead (See previous messages
on this list
> for the earlier discussion) and I am reluctant to facilitate over-use.
>   2) An update can be performed easily using boinc_cmd or with my
> soon-to-be=released REXX version of boinc_cmd.  So keeing it out of
(Continue reading)

Permalink | Reply | 7 comments |
headers
John Small | 19 Jan 2006 15:57

REXXRPC v1.0

As I've mentioned earlier on this list, I have been working on a REXX program
which communicates with the Boinc client using TCPI/IP sockets.  I have
uploaded it to the files section.

It does most of what BOINC_CMD does, and more.  Here's a snippet from the
"readme":
   REXXRPC is a REXX version of and extension to BOINC_CMD.
   The primary reasons for its release:
      1) To be used as a subroutine by other utilities.
         This encapsulates the RPC code into a single
         source making maintenance easier and it
         facilitates the creation of utilities in the
         future.
      2) To provide a standalone program which provides
         a) the complete response from the Boinc client
         b) a more extensive set of commands
         c) more complete, easier-to-use and correct help
         d) verification before executing potentially 
            destructive commands

Included in the archive is a couple of utilities which I hope will provide
clues as to how this utility can be used.

Please "kick the tires" on this and let me know about
  bugs
  customizations you'd like
  the help screens
  the commands you never saw in BOINC_CMD help
  feature requests
  which yet-to-be-implemented commands of BOINC_CMD need to be implemented (or
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Small | 19 Jan 2006 15:57

Still there?

No messages in a day and a half?  Is this list working?

--

-- 
John Small

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/seti-warp/

<*> To unsubscribe from this group, send an email to:
    seti-warp-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
Permalink | Reply | 0 comments |
headers
Robert Gammon | 19 Jan 2006 19:26
Picon
Favicon

Re: REXXRPC v1.0

Like what I see so far.  Copied to a utility directory on this machine 
that is already in the path (\programs\boinc5\bin is not in the path nor 
do I want it to be.)

Standalone, it only is a substitute for boinc_cmd.   When you release a 
future version of JBSWU_Monitor that has the hooks to call rexxrpc.cmd, 
then it becomes a very useful tool indeed.

The restriction of not being able to pass a command line url to it is a 
strong dislike, imposed by the REXX interpreter.  This makes it 
difficult to test the most used function boinc_cmd (at least for me)

When you update this utility, I  will keep it in my utils.os2 directory 
to be accessed by future versions of JBSWU_Monitor

--

-- 
<http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=190817> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/seti-warp/

<*> To unsubscribe from this group, send an email to:
    seti-warp-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
(Continue reading)

Permalink | Reply | 3 comments |
headers
John Small | 19 Jan 2006 22:49

Re: REXXRPC v1.0

** Reply to message from Robert Gammon <rgammon51 <at> yahoo.com> on Thu, 19 Jan
2006 12:26:43 -0600

>Standalone, it only is a substitute for boinc_cmd.

Actually I find that is does have some advantages as a standalone:
  1) Additional commands
  2) Better help
  3) More complete responses
  4) Verification of potenially harmful actions

>When you release a 
>future version of JBSWU_Monitor that has the hooks to call rexxrpc.cmd, 
>then it becomes a very useful tool indeed.

This is its primary purpose in life.

>The restriction of not being able to pass a command line url to it is a 
>strong dislike, imposed by the REXX interpreter.

First, there is NO restriction when REXXRPC is used as a subroutine of
another program.  So, for example, running project update from jbswu_monitor
will seem natural.

When REXXRPC is run as a standalone program it is not impossible to pass a url,
just a little awkward.  The "readme" gives 3 workarounds (which still use
REXXRPC):
  1) pass 'setiathome.berkeley.edu' instead of 'http://...'
  2) use rexxrpc2
  3) pass arguments in an environment variable.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Gammon | 20 Jan 2006 00:14
Picon
Favicon

Re: REXXRPC v1.0

John Small wrote:
> ** Reply to message from Robert Gammon <rgammon51 <at> yahoo.com> on Thu, 
> 19 Jan
> 2006 12:26:43 -0600
>
> >Standalone, it only is a substitute for boinc_cmd.
>
> Actually I find that is does have some advantages as a standalone:
>   1) Additional commands
>   2) Better help
>   3) More complete responses
>   4) Verification of potenially harmful actions
>
Yes, since we see the complete RPC response versus NOTHING from 
BOINC_cmd, IT IS BETTER and warns of potentially dangerous actions 
(update, reset, detach to name a few).

Update is one such command that produces a NULL response on success from 
boinc_cmd

> >When you release a
> >future version of JBSWU_Monitor that has the hooks to call rexxrpc.cmd,
> >then it becomes a very useful tool indeed.
>
> This is its primary purpose in life.
>
> >The restriction of not being able to pass a command line url to it is a
> >strong dislike, imposed by the REXX interpreter.
>
> First, there is NO restriction when REXXRPC is used as a subroutine of
(Continue reading)

Permalink | Reply | 1 comment |
headers
kemyers91384 | 20 Jan 2006 00:35
Picon

Re: No WU available message in JBSWU_Monitor

--- In seti-warp <at> yahoogroups.com, "John Small" <jsmall <at> o...> wrote:

John, I tried the fix you detailed below but the monitor does not run.
It throws up an error immediately on the line that was changed. How
close are you to the next release that fixes this bug?  I have one
workstation that is showing the no wu available message again even
though it has 4 wu's cached and is currently processing another.

Keith

> I believe I have found this bug.  A complete fix for this will be
uploaded
> within the next day (I am in the middle of preparing the next
release).  
> 
> In the meantime, a "quick and dirty" fix is to change the line:
>       if (wu_queued = 0) then
> to
>       if (wu_queued = -1) then
> 
> See how this works for you.  It should work well as long as there is
a WU being
> processed.
> 
> -- 
> John Small
>

 
Yahoo! Groups Links
(Continue reading)

Permalink | Reply | 2 comments |

Gmane