Hi Guys,
Using Q4OS Trinity Desktop. Systemd is becoming a nuisance.
Where do you alter the timeout for Systemd.
Thanks in advance, in particular the developers and maintainers of Trinity.
Am Samstag, 27. Juli 2019 schrieb Baron:
Hi Guys,
Using Q4OS Trinity Desktop. Systemd is becoming a nuisance.
Where do you alter the timeout for Systemd.
Thanks in advance, in particular the developers and maintainers of Trinity.
Hi Baron,
I have read about some appearances of a bug causing systemd slowing down shutdown/reboot on debian-user and/or debian-devel, if that is what you mean.
As I don't use systemd I deleted those mails and can't give you a reference, unfortunately. You can try to search the web for "systemd timeout shutdown" or similar. Maybe this could help:
https://unix.stackexchange.com/questions/328317/reducing-shutdown-timeout-fo...
HTH
Kind regards, Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2019/07/27 06:53 PM, Stefan Krusche wrote:
Am Samstag, 27. Juli 2019 schrieb Baron:
Hi Guys,
Using Q4OS Trinity Desktop. Systemd is becoming a nuisance.
Where do you alter the timeout for Systemd.
Thanks in advance, in particular the developers and maintainers of Trinity.
You can uncomment the line with DefaultTimeoutStartSec and DefaultTimeoutStopSec in /etc/systemd/system.conf
DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s
Works like a charm.
Cheers Michele
On Saturday 27 July 2019 14.38:19 Michele Calgaro via trinity-users wrote:
You can uncomment the line with DefaultTimeoutStartSec and DefaultTimeoutStopSec in /etc/systemd/system.conf
DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s
Works like a charm.
Cheers Michele
I tried this on a Toshiba z20t and the result was to drop me to a command line (although ctrl-D let me continue).
I then tried increasing both timouts to 10s and... it worked.
So one might experiment with different values on different computers...
Thierry
Hi Thierry,
On Thursday 08 August 2019 16:51:58 Thierry de Coulon wrote:
On Saturday 27 July 2019 14.38:19 Michele Calgaro via trinity-users
wrote:
You can uncomment the line with DefaultTimeoutStartSec and DefaultTimeoutStopSec in /etc/systemd/system.conf
DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s
Works like a charm.
Cheers Michele
I tried this on a Toshiba z20t and the result was to drop me to a command line (although ctrl-D let me continue).
I then tried increasing both timouts to 10s and... it worked.
So one might experiment with different values on different computers...
Thierry
Since adding that file and giving it a 15 second time out, I have not had a single stop job !
Anno domini 2019 Thu, 8 Aug 17:39:00 +0100 Baron scripsit:
Hi Thierry,
On Thursday 08 August 2019 16:51:58 Thierry de Coulon wrote:
On Saturday 27 July 2019 14.38:19 Michele Calgaro via trinity-users
wrote:
You can uncomment the line with DefaultTimeoutStartSec and DefaultTimeoutStopSec in /etc/systemd/system.conf
DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s
Works like a charm.
Cheers Michele
I tried this on a Toshiba z20t and the result was to drop me to a command line (although ctrl-D let me continue).
I then tried increasing both timouts to 10s and... it worked.
So one might experiment with different values on different computers...
Thierry
Since adding that file and giving it a 15 second time out, I have not had a single stop job !
Sorry guys, but does this sound like propper software or more like crap?
Nik
On Thursday 08 August 2019 18.51:12 Dr. Nikolaus Klepp wrote:
Sorry guys, but does this sound like propper software or more like crap?
Nik
I agree with you... However it seems removing systemd is no more an alternative on Buster - I'll have to wait for Devuan to catch up.
I'm not ready to try development Beowulf yet.
If I have time I may take a look at Gentoo again - seems they have some TDE available. And I rather like Debian.
Thierry
Hi Thierry,
Anno domini 2019 Thu, 8 Aug 21:22:05 +0200 Thierry de Coulon scripsit:
On Thursday 08 August 2019 18.51:12 Dr. Nikolaus Klepp wrote:
Sorry guys, but does this sound like propper software or more like crap?
Nik
I agree with you... However it seems removing systemd is no more an alternative on Buster - I'll have to wait for Devuan to catch up.
I'm not ready to try development Beowulf yet.
even when Beowulf has not been released officially yet, it's as stable as it will get on i386 and amd64 :)
Nik
If I have time I may take a look at Gentoo again - seems they have some TDE available. And I rather like Debian.
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Guys,
Thank you for your replies.
On Saturday 27 July 2019 11:19:17 Baron wrote:
Hi Guys,
Using Q4OS Trinity Desktop. Systemd is becoming a nuisance.
Where do you alter the timeout for Systemd.
Thanks in advance, in particular the developers and maintainers of Trinity.
Michele, "system.conf" doesn't exist in either /etc/systemd/ or /lib/systemd on my machine. However there are dozens of systemd files in "/lib" almost all of them are binary files.
Deloptes, I get "stop jobs" sometimes on startup but most often on shut down, it may do a stop job several times or I just hard kill it by switching off.
It seems to have become worse lately.
Thanks:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Using Q4OS Trinity Desktop. Systemd is becoming a nuisance.
Michele, "system.conf" doesn't exist in either /etc/systemd/ or /lib/systemd on my machine. However there are dozens of systemd files in "/lib" almost all of them are binary files.
Hi Baron, I don't use Q4OS but it is based on Debian, so it seems weird there is no system.conf file in /etc/systemd. Perhaps their setup is a bit different, but in such case you will need to look around for a file like that, which contains systemd configuration.
Cheers Michele
Hi Deloptes,
On Sunday 28 July 2019 05:50:30 deloptes wrote:
Baron wrote:
Deloptes, I get "stop jobs" sometimes on startup but most often on shut down, it may do a stop job several times or I just hard kill it by switching off.
But which jobs are hanging?
It varies. Sometimes its to do with setting remote printers, others its the graphics.
I've not yet found a config file for systemd that I can edit the time delay. I did find the one in "/lib" for tdm.service, which I edited out the "Conflicts=getty@tty7.service plymouth-quit.service" line. But its made no difference.
Suggestions from people on the Q4OS forums are to update to the latest version. I'm currently two or three versions behind.
If you don't have a "system.conf" and friends, it probably means you are using the defaults. That file usually ships with all the lines commented out by default. You could try creating an /etc/systemd/system.conf file
[Manager] DefaultTimeoutStopSec=5s
That might not be a great thing to do for all processes (think database server wanting to finish an operation or something) but in most cases if something isn't going to die in 5 seconds, it's probably not going to if it waits 90.
On Sun, Jul 28, 2019 at 1:06 AM Baron baron@linuxmaniac.net wrote:
Hi Deloptes,
On Sunday 28 July 2019 05:50:30 deloptes wrote:
Baron wrote:
Deloptes, I get "stop jobs" sometimes on startup but most often on shut down, it may do a stop job several times or I just hard kill it by switching off.
But which jobs are hanging?
It varies. Sometimes its to do with setting remote printers, others its the graphics.
I've not yet found a config file for systemd that I can edit the time delay. I did find the one in "/lib" for tdm.service, which I edited out the "Conflicts=getty@tty7.service plymouth-quit.service" line. But its made no difference.
Suggestions from people on the Q4OS forums are to update to the latest version. I'm currently two or three versions behind.
-- Best Regards: Baron
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Guys,
Thank you for your replies.
On Sunday 28 July 2019 07:05:13 Snidely Whiplash wrote:
If you don't have a "system.conf" and friends, it probably means you are using the defaults. That file usually ships with all the lines commented out by default. You could try creating an /etc/systemd/system.conf file
[Manager] DefaultTimeoutStopSec=5s
That might not be a great thing to do for all processes (think database server wanting to finish an operation or something) but in most cases if something isn't going to die in 5 seconds, it's probably not going to if it waits 90.
Right, I've done that, just have to wait and see what happens. It doesn't always do a stop job, It didn't this morning when I switched off.
I'll reports back.
Hi Guys,
On Sunday 28 July 2019 09:26:08 Baron wrote:
Hi Guys,
Thank you for your replies.
On Sunday 28 July 2019 07:05:13 Snidely Whiplash wrote:
If you don't have a "system.conf" and friends, it probably means you are using the defaults. That file usually ships with all the lines commented out by default. You could try creating an /etc/systemd/system.conf file
[Manager] DefaultTimeoutStopSec=5s
That might not be a great thing to do for all processes (think database server wanting to finish an operation or something) but in most cases if something isn't going to die in 5 seconds, it's probably not going to if it waits 90.
Right, I've done that, just have to wait and see what happens. It doesn't always do a stop job, It didn't this morning when I switched off.
I'll report back.
Well its been a week now and I've not had a single stop job ! The machine seems to be working well since adding the conf file.
Thanks all for the help.
-
Baron -
deloptes -
Dr. Nikolaus Klepp -
Michele Calgaro via trinity-users -
Snidely Whiplash -
Stefan Krusche -
Thierry de Coulon