Hmmm Problems Rebooting and Something else.

Posted by Celes on Mon 16 Jun 2003 07:09 AM — 5 posts, 20,146 views.

#0
Well I seem to have resolved some issues with having to keep those mean Cygwin terminals on (Only on all NT based systems aka NT/2000/XP), by simply activating Cygwin "Deamon Mode" (You need to start up the Cygwin Process(es) Server - cygserver.exe you can easily install it as service by using cygrunsrv didn't try the normal way yet), that way you can run the ./startup script *almost* efficently and quit the Terminal Window without quitting all processes "attached".

I stated that you CAN actually run the script almost efficently because it seemed to work at the first shoots but then it stopped for some reason. I removed all limit commands within the script meaning it should work theoretically... yet somethin' went wrong.

Did anyone of you try this method and could give me some feedback?

Thanks.
#1
Hmmm never mind, probably either something fooled me or I made an exception I'm now unable to repeat (it's worth testing though anyways), I'll try to run the script using cygrunsrv without having it quit.
#2
Hmmm well cygrunsrv is unable (tried 3 different methods, without success) to keep alive bash processes in the background :/

Enough testing, I'm open to any suggestion if you got any *XD*.
USA #3
ick. Running Cygwin as a background process? I doubt many people here have toyed with the idea much. I'd reccommend using native linux before I'd reccommend trying to get a *nix API to run via a Windows service. But, giving your reasons the benefit of the doubt, I'd say the Cygwin website would be a good place to find this answer. Or if you're running stock SMAUG, find the version that's compiled to run as a Windows service (I'm quite certain it's available for download on this site). Just my 2 cents.
#4
Baborak,

You can run *nix services compatible with cygwin through the cygrunsrv utility, meaning that I can run SMAUG stand-alone as service as long as I don't use the reboot command :D.

The problem comes into be with batch bash programs, such as the "startup" script which uses tcsh... cygrunsrv seems to be unable to keep the process alive after starting it (though it should go directly in what is the background being ran us "tcsh -f /smaug/src/startup &"), as simply the program runs fine but as (it seems again) cygrunsrv doesn't recognize batches the service runner simply exits after the last batch command is executed (without starting the loop) thus terminating all the linked processes.