Re: A stop job is running for Entropy Gatherer Daemon? Really?

On 5/5/19 6:07 AM, Tom Horsley wrote: But the service knows that. Why isn't there a way to tell systemd that in the .service file? There's no use case for it.  rngd is expected to terminate (more or less) immediately after it gets sigterm.  If there were another directive to ignore shutdown

Re: A stop job is running for Entropy Gatherer Daemon? Really?

Tom Horsley writes: On Sat, 4 May 2019 22:12:11 -0600 Joe Zeff wrote: > Because systemd has no way of knowing what the service is doing or that > it's safe to kill it without waiting for it to finish. But the service knows that. Why isn't there a way to tell systemd that in the .service file?

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On Sat, 4 May 2019 22:12:11 -0600 Joe Zeff wrote: > Because systemd has no way of knowing what the service is doing or that > it's safe to kill it without waiting for it to finish. But the service knows that. Why isn't there a way to tell systemd that in the .service file?

Re: A stop job is running for Entropy Gatherer Daemon? Really?

Allegedly, on or about 4 May 2019, Tom Horsley sent: > Though a sane person might ask, "Why is it the right thing to wait > for a service gathering information which will be utterly discarded > on the reboot anyway?" Well, much as I hate to defend systemd, *it* doesn't know that *that* service is

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On 05/04/2019 08:20 PM, Tom Horsley wrote: On Sat, 4 May 2019 18:58:32 -0700 Gordon Messmer wrote: We don't need tortured logic to blame systemd.  It's doing the right thing. Though a sane person might ask, "Why is it the right thing to wait for a service gathering information which will be

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On Sat, 4 May 2019 18:58:32 -0700 Gordon Messmer wrote: > We don't need tortured logic to blame systemd.  It's doing the right > thing. Though a sane person might ask, "Why is it the right thing to wait for a service gathering information which will be utterly discarded on the reboot anyway?"

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On 5/4/19 4:13 PM, Sam Varshavchik wrote: In the good-old days, when integrating some new gizmo like rngd, by the nature of the beast you'll always check into how it works and make a minimal effort to learn its basics. Basic due diligence. From the linked bugzilla bug, it seems that rngd was

Re: A stop job is running for Entropy Gatherer Daemon? Really?

Samuel Sieb writes: On 5/4/19 9:32 AM, Sam Varshavchik wrote: How can you possibly get stopping a piddly daemon, like rngd, wrong? Who knows. It's brain damage. As usual, it is not a systemd problem, unless you consider that trying to do a clean shutdown is brain damage. The rngd

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On 5/4/19 9:32 AM, Sam Varshavchik wrote: I just wait 90 seconds, in those instances, and write it off as yet another systemd brain damage. According to systemd.service man page, TimeoutStopSec sets this timeout. So you can add that to rngd.service, I suppose. Or, if you want to bring out

Re: A stop job is running for Entropy Gatherer Daemon? Really?

On Sat, 04 May 2019 12:32:59 -0400 Sam Varshavchik wrote: > Maybe 1 in every 20 if my reboots gets held up for "stopping user processes". That happens to me so often that I built an entire big hammer from scratch just to hit the system with when I reboot: https://tomhorsley.com/game/punch.html

Re: A stop job is running for Entropy Gatherer Daemon? Really?

Tom Horsley writes: I'm frequently rebooting my new fedora 30 install as I test things, and on one reboot I got the entire boot process held up by a stop job for rngd.service. I'm rebooting for God's sake. Why do you need to stop the reboot process to wait till you've gathered enough entropy

Re: A stop job is running for Entropy Gatherer Daemon? Really?

I guess this is probably this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1690364 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: a stop job is running....

On Sun, Sep 18, 2016 at 9:58 AM, François Patte wrote: > Le 17/09/2016 22:53, Jon LaBadie a écrit : >> On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote: >>> Tom Horsley wrote: >>> Because systemd has a gazillion bugs like this >>> >>> In cases

Re: a stop job is running....

Le 17/09/2016 22:53, Jon LaBadie a écrit : > On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote: >> Tom Horsley wrote: >> >>> Because systemd has a gazillion bugs like this >> >> In cases like this in general, it's not systemd, >> but the individual services that have bugs. >> > Does

Re: a stop job is running....

On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote: > Tom Horsley wrote: > > > Because systemd has a gazillion bugs like this > > In cases like this in general, it's not systemd, > but the individual services that have bugs. > Does anyone else tire of hearing "its not systemd, its ..."

Re: a stop job is running....

On Sat, 17 Sep 2016 11:34:54 -0500 Rex Dieter wrote: > In this particular case, it's the user session that has processes still > running, and not quiting after logout. There were no "user daemons" till systemd invented them. Every login creates at least a "systemd --user" process which never

Re: a stop job is running....

Tom Horsley wrote: > On Thu, 15 Sep 2016 23:40:19 +0200 > François Patte wrote: > >> Why theses messages? > > Because systemd has a gazillion bugs like this In cases like this in general, it's not systemd, but the individual services that have bugs. In this particular case, it's the user

Re: a stop job is running....

On Thu, 2016-09-15 at 23:40 +0200, François Patte wrote: > And it takes ages to shutdown > > Why theses messages? > > today I started rc.local compatibility then I stopped it and at > shutdown, I get the message: "a stop job is running for this > service" which has been stopped one hour

Re: a stop job is running....

Tom Horsley wrote: > Read about it here: http://tomhorsley.com/game/punch.html LOL Actually, I'm pretty happy with systemd h/t To think of the hours I used to spend finding out about daemons I never used and what they were for, setting them all up to either run or not run, etc... Sure, I

Re: a stop job is running....

In my case, when it shows up, it never last more than a couple of minutes. But yeah, it's been ages with this problem. Cheers, Sylvia -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options:

Re: a stop job is running....

I filed this bug in Fedora years ago. Unhappy to see it still is not fixed On Thu, Sep 15, 2016 at 7:42 PM, Terry Polzin wrote: > I've noticed an issue trying to shutdown when there are NFS and CIFS mounts > > On Thu, Sep 15, 2016 at 5:50 PM, Tom Horsley

Re: a stop job is running....

On Thu, 15 Sep 2016 19:42:00 -0400 Terry Polzin wrote: > I've noticed an issue trying to shutdown when there are NFS and CIFS mounts I've developed my own reboot alias that kills off all the things I've been able to track down as sources of hangs before asking systemd to reboot. It works pretty

Re: a stop job is running....

I've noticed an issue trying to shutdown when there are NFS and CIFS mounts On Thu, Sep 15, 2016 at 5:50 PM, Tom Horsley wrote: > On Thu, 15 Sep 2016 23:40:19 +0200 > François Patte wrote: > > > Why theses messages? > > Because systemd has a gazillion bugs like this and

Re: a stop job is running....

On Thu, 15 Sep 2016 23:40:19 +0200 François Patte wrote: > Why theses messages? Because systemd has a gazillion bugs like this and they are having so much fun introducing yet more bugs that they aren't remotely interested in making what they have actually work correctly. I have noticed that