Christopher Faylor wrote:
> Wouldn't "ps -W" and "/bin/kill -f" work here, too?
Probably. Though ps doesn't tell you which cygrunsrv is which, if you
have more than one running and don't want to kill an innocent service,
which is why I use procexp. "procps aux --forest" works too.
Brian
--
Un
On Thu, Apr 21, 2005 at 02:21:39PM -0700, Brian Dessent wrote:
>"Thompson, Lloyd D. (SSD)" wrote:
>
>> $ net stop syslogd
>> The service could not be controlled in its present state.
>>
>> More help is available by typing NET HELPMSG 2189.
>>
>> $ net helpmsg 2189
>>
>> The service could not be
"Thompson, Lloyd D. (SSD)" wrote:
> $ net stop syslogd
> The service could not be controlled in its present state.
>
> More help is available by typing NET HELPMSG 2189.
>
> $ net helpmsg 2189
>
> The service could not be controlled in its present state.
I do not know the root cause for why th
Hello,
I'm trying to start the cygwin syslog daemon. I set it up using
syslogd-config, then try and start it with either "net start" or
"cygrunsrv -S". The service never fully starts. The return of both
commands states that the service could not be started.
It does however hang in start up mod
4 matches
Mail list logo