Andrey Borzenkov wrote:
В Tue, 01 Jan 2013 23:37:56 -0700
JB пишет:
Andrey Borzenkov wrote:
В Tue, 01 Jan 2013 18:52:38 -0700
JB пишет:
Thanks! I'll try and it may work in my case. What's interesting is
that in your case it sounded like rsyslog was hanging around while
В Tue, 01 Jan 2013 23:37:56 -0700
JB пишет:
> Andrey Borzenkov wrote:
> > В Tue, 01 Jan 2013 18:52:38 -0700
> > JB пишет:
> >
> >
> >> Thanks! I'll try and it may work in my case. What's interesting is
> >> that in your case it sounded like rsyslog was hanging around while it
> >> was hav
Andrey Borzenkov wrote:
В Tue, 01 Jan 2013 18:52:38 -0700
JB пишет:
Thanks! I'll try and it may work in my case. What's interesting is
that in your case it sounded like rsyslog was hanging around while it
was having problems dealing with the condition of having the network
unavailable.
В Tue, 01 Jan 2013 18:52:38 -0700
JB пишет:
> Thanks! I'll try and it may work in my case. What's interesting is
> that in your case it sounded like rsyslog was hanging around while it
> was having problems dealing with the condition of having the network
> unavailable. In my case, webrickd
Thanks! I'll try and it may work in my case. What's interesting is
that in your case it sounded like rsyslog was hanging around while it
was having problems dealing with the condition of having the network
unavailable. In my case, webrickd actually stops and shuts down almost
immediately but
Am 02.01.2013 01:27, schrieb JB:
> Hello all,
>I do have one more question about systemd. Sometimes, it takes a really
> really long time to get a service to
> stop or restart. Othertimes, it doesn't. Now, when it does take a long time
> I get entires in the logs such as this:
>
> Jan
Hello all,
I do have one more question about systemd. Sometimes, it takes a
really really long time to get a service to stop or restart.
Othertimes, it doesn't. Now, when it does take a long time I get
entires in the logs such as this:
Jan 1 16:23:42 localhost systemd[1]: webrickd.serv
