Danny Backx wrote:
> 
> I've hacked rshd.c a bit so it has a UI, this has the benefit of making
> the process visible in the WinCE process list. The UI is only half done,
> it has toggles to set the command line options that you had in the
> source, but I've not hooked the toggles to the variables yet. Should be
> easy though.
> 

Errr, no, please don't do it this way.  Rshd is supposed to be a service.
It should be running without a gui.  I would ratter move the GUI you are
developing into a control panel applet.  Take a look at Pocket Console or
the telnet client downloadable from their page for examples.  The applet could
then have a "stop" button that kills rshd.  To get at the
process to kill, you can either enumerate all the processes running, or have
rshd.exe write its pid to a file on startup, or to the registry.  Alternatively,
you could send a WM_QUIT to rshd, or broadcast a special private
windows message but these require adding a message loop to rshd.  There are even
other perhaps better ways to do it, like move rshd into a services.exe service.
This is more or less again what I said the last time we talked about it ...

A small step in the right direction would be to have a -q (quiet) option to
make rshd not do any printfs so the console doesn't pop up, or implement a NUL:
device, and from the applet start rshd with io redirected to NUL: .  The former
is perhaps best - less pollution.

> Also I've not been able to spend time on the incomplete "spaces in
> command lines" patch, so that's still at the state I left it the other
> time, please disregard that.
> 

I think you need to svn up.  I see code in the patch for the
CreatePipe failure handling that is already fixed in svn?

Cheers,
Pedro Alves



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to