I'll remove that particular limit in the next client.
The limit will then be a bit less than 64KB,
which is the size of the database blob used to store the
WU's XML description, which includes the cmdline.
-- David

On 22-Mar-2011 6:47 AM, Travis Desell wrote:
> Think I've found a rather nasty bug.
>
> I was trying to send some data through the command line parameters (one of
> the parameters is pretty large, maybe 10-15k characters) and it seems to
> crash the BOINC client/manager.
>
> A window with "Communicating with BOINC client. Please wait..." keeps popping
> up, and the only way to get out of it is to quit the BOINC manager.  Making
> matters worse it happens every time the manager opens up, so you can't really
> do anything with it.
>
> So a couple questions:
>
> 1. is there a hard limit on the size of command line parameters? and 2. how
> can I kill the workunits that aren't allowing the manager to communicate with
> the client, so I can get the boinc manager/client working again?
>
>
> ----------------------------------------------------------------------------------------------------------
>
>
Travis Desell<deselt @ cs.rpi.edu>                       1-518-867-1054
> Adjunct Professor&  Postdoctoral Research Assistant Rensselaer Polytechnic
> Institute, 110 8th Street, Troy NY 12180, USA http://www.cs.rpi.edu/~deselt/
> MilkyWay@Home ( http://milkyway.cs.rpi.edu/ ) DNA@Home (
> http://dnahome.cs.rpi.edu/ ) Worldwide Computing Laboratory (
> http://wcl.cs.rpi.edu/ )
> ----------------------------------------------------------------------------------------------------------
>
>  _______________________________________________ boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe,
> visit the above URL and (near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to