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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
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
