problem with starting services in 1.5.19
Yadin Y. Goldschmidt
yadin@pitt.edu
Mon Feb 27 19:38:00 GMT 2006
"Igor Peshansky" pechtcha@XXX wrote in message news:
> On Mon, 27 Feb 2006, Yadin Y. Goldschmidt wrote:
>
>> See comments below
>> "Igor Peshansky" pechtcha@XXXXXX wrote in message news:
>> > Ugh, top-posting... Reformatted.
>> >
>> > On Mon, 27 Feb 2006, Yadin Y. Goldschmidt wrote:
>> >
>> > > The problem is very similar to problems Igor Peschansky and others
>> > > had
>> > > in the past with XP SP1, apparently because of changes made on 01/04
>> > > concerning fhandler_console?
>> >
>> > That was due to a Cygwin bug that has since been fixed.
>> >
>> > > I run SP2 but I still have a problem. If I only run one service on
>> > > reboot it will start but if I try to run 2 services on reboot one
>> > > would
>> > > hang.
>> > >
>> > > From the command line none will start. There is nothing in cron.log
>> > > or
>> > > sshd.log since they don't even start. No I don't run any firewall
>> > > besides xp built in firewall and Symantec corporate antivirus. As I
>> > > said
>> > > there is no problem at all with 1.5.18 and I never had any problems
>> > > before. This is very frustrating.
>> >
>> > When you say "none will start from the command line", what is the exact
>> > command line you're using? Are you starting them as SYSTEM, or as a
>> > regular user?
>>
>> from the command line I mean typing
>> cygrunsrv -S cron
>> or
>> cygrunsrv -S shhd
>> it starts with 1.5.18. Eith 1.5.19 I get
>> "cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error
>> 1053:
>> The service did not respond to the start or control request in a timely
>> fashion"
>> and there is a hanged cygrunsrv in "ps -a"
>> PID PPID PGID WINPID TTY UID STIME COMMAND
>> 2004 1 2004 2004 con 1004 11:38:52 /usr/bin/bash
>> 164 1 164 164 ? 18 11:39:10 /usr/bin/cygrunsrv
>> 2384 2004 2384 3600 con 1004 11:39:26 /usr/bin/ps
>> with no cron or shhd.
>> Now I run it as a user with Administrative power. I don't know how to
>> open a
>> bash shell
>> as SYSTEM. How do you do that?
>
> Googling for "syste-owned shell" (with quotes) points your right at the
> thread with the relevant shortcut.
>
>> > > Were the changes to fhandler_console really necessary?
>> > > Any other suggestions? Igor, Larry, Chris?
>> >
>> > Try opening a SYSTEM-owned bash shell and starting the service program
>> > explicitly, with the same arguments that cygrunsrv would give it (see
>> > "cygrunsrv --verbose -Q SERVICENAME" for those arguments). If this
>> > doesn't work either, we've ruled out cygrunsrv.
>> As I said I dont know how to open a SYSTEM-owned bash shell
>
> Let us know if the above works for you.
OK Here are results in a system-owned shell:
MINERVA(~)$ /usr/sbin/cron -D
[2452] cron started
I hit Conrol C
MINERVA(~)$ ps -a
PID PPID PGID WINPID TTY UID STIME COMMAND
3084 1 3084 3084 con 18 12:13:00 /usr/bin/bash
2880 3084 2880 2324 con 18 12:14:37 /usr/bin/ps
MINERVA(~)$ cygrunsrv -S cron
MINERVA(~)$ ps -a
PID PPID PGID WINPID TTY UID STIME COMMAND
3084 1 3084 3084 con 18 12:13:00 /usr/bin/bash
3200 1 3200 3200 ? 18 12:14:59 /usr/bin/cygrunsrv
3396 3200 3396 900 ? 18 12:14:59 /usr/sbin/cron
3432 3084 3432 912 con 18 12:15:08 /usr/bin/ps
MINERVA(~)$ cygrunsrv -S sshd
cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1053:
The service did not respond to the start or control request in a timely
fashion
PID PPID PGID WINPID TTY UID STIME COMMAND
3084 1 3084 3084 con 18 12:13:00 /usr/bin/bash
2700 1 2700 2700 ? 18 12:56:26 /usr/bin/cygrunsrv
2280 3084 2280 2888 con 18 12:56:46 /usr/bin/ps
MINERVA(~)$ kill -9 2700
MINERVA(~)$ cygrunsrv --verbose -Q sshd
Service : sshd
Display name : CYGWIN sshd
Current State : Stopped
Command : /usr/sbin/sshd -D
stdin path : /dev/null
stdout path : /var/log/sshd.log
stderr path : /var/log/sshd.log
Environment : CYGWIN="ntsec"
Process Type : Own Process
Startup : Automatic
Account : LocalSystem
MINERVA(~)$ /usr/sbin/sshd -D
>From another window
MINERVA(~)$ ps -a
PID PPID PGID WINPID TTY UID STIME COMMAND
3084 1 3084 3084 con 18 12:13:00 /usr/bin/bash
3516 3084 3516 3396 con 18 13:57:36 /usr/sbin/sshd
3964 1 3964 3964 con 1004 13:57:58 /usr/bin/bash
3568 3964 3568 2080 con 1004 13:58:07 /usr/bin/ps
So you see that from a SYSTEM account the first service starts but second
service hangs.
If I use a bash shell own by me even rhe first does not start.
If one does not use cygrunsrv both cron and sshd start.
Yadin.
> Igor
> --
> http://cs.nyu.edu/~pechtcha/
> |\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
> ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
> |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
> '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
>
> "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends
> compte."
> "But no -- you are no fool; you call yourself a fool, there's proof enough
> in
> that!" -- Rostand, "Cyrano de Bergerac"
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list