I run the BOINC client. Its .service file allows it 1.5 minutes to shut
down. Observed time is about 1 minute. If I shut it down with
systemctl before rebooting, it takes the same length of time.
Naturally, that time is added to the total shutdown time. Without
BOINC, the computer shuts down as quickly as I would expect.

I don't think I can do anything about this, but at least I know the
reason. I thought that sharing it might help others.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Sat, 4 Jul 2020 14:17:30 +1000, Doug Laidlaw wrote:

I run the BOINC client. Its .service file allows it 1.5 minutes to shut down. Observed time is about 1 minute. If I shut it down with
systemctl before rebooting, it takes the same length of time.
Naturally, that time is added to the total shutdown time. Without
BOINC, the computer shuts down as quickly as I would expect.

I don't think I can do anything about this,

But I suggest you can. I know nothing about BOINC, but if it were I,
I would send a sig term signal and see how long it takes to terminate.
I would be surprised if longer that 20 seconds.

Once I had a reasonable time I would create a drop-in file with the
desired timeout value.

For example I do not like the 300 second timeout for mysqld so I arbitrarily picked 150.

Anytime you want to create a drop-in file use;
systemctl edit whatever_unit_file_here
and just enter what you want changed in a given section.

Whatever you put in drop-in files override the same item in the unit file.

As an example you might do something like
systemctl edit boinc-client.service
and add something like

[Service]
# Give a reasonable amount of time for the client to start up/shut down TimeoutSec=150

I would then stop the service, run
systemctl --system daemon-reload
systemctl start boinc-client
systemctl status boinc-client

That should show you Drop-In: with the new directory and drop-in file.

I can recommend creating install and change scripts to automate
configuration of an install.

Personally I put xx__ in all my configuration file names where possible.
Makes it easy to do something like locate xx__ to find them.
Examples:
/etc/exports.d/xx__local.exports
/usr/lib/systemd/network/10_xx__enp3s0.network

At the moment I have
$ locate xx__ | grep -v /local/bin/ | wc -l
32
drop-in files.





--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 4/7/20 8:32 pm, Bit Twister wrote:

run the BOINC client. Its .service file allows it 1.5 minutes to shut
down. Observed time is about 1 minute. If I shut it down with
systemctl before rebooting, it takes the same length of time.
Naturally, that time is added to the total shutdown time. Without
BOINC, the computer shuts down as quickly as I would expect.

I don't think I can do anything about this,

But I suggest you can. I know nothing about BOINC, but if it were I,
I would send a sig term signal and see how long it takes to terminate.
I would be surprised if longer that 20 seconds.

I ran shutdown in the verbose mode, no "splash quiet", and watched the countdown for the stop job. It took about one minute. The maximum is 1
min 30 secs, but I assume that if there is nothing to do after 60
seconds, shutdown moves along. Certainly I can fix a shorter time, and
simply kill the job, but I don't know what difference it would make. At
the worst, it could make the current work unit restart, or discard it.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 4/7/20 11:23 pm, Doug Laidlaw wrote:

On 4/7/20 8:32 pm, Bit Twister wrote:

  run the BOINC client.  Its .service file allows it 1.5 minutes to shut >>> down.  Observed time is about 1 minute.  If I shut it down with
systemctl before rebooting, it takes the same length of time.
Naturally, that time is added to the total shutdown time.  Without
BOINC, the computer shuts down as quickly as I would expect.

I don't think I can do anything about this,

But I suggest you can. I know nothing about BOINC, but if it were I,
I would send a sig term signal and see how long it takes to terminate.
I would be surprised if longer that 20 seconds.

I ran shutdown in the verbose mode, no "splash quiet", and watched the countdown for the stop job.  It took about one minute.  The maximum is 1 min 30 secs, but I assume that if there is nothing to do after 60
seconds, shutdown moves along.  Certainly I can fix a shorter time, and simply kill the job, but I don't know what difference it would make.  At the worst, it could make the current work unit restart, or discard it.

By way of explanation, BOINC started life as setiathome. It is a
distributed computing scheme. Data is sent to it for processing, in
chunks, called work units. If I discard a work unit, it is sent to a different subscriber. The client program runs in the background,
although there is a graphical viewer.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Sat, 4 Jul 2020 23:23:47 +1000, Doug Laidlaw wrote:

I ran shutdown in the verbose mode, no "splash quiet", and watched the countdown for the stop job.

That is not what I said to do. The process could be stopped, yet systemd
does not know that and continues until timeout value.

You have already indicated that when you said it took the same shutdown
time when you have already stopped it.

man kill, to see how to send the terminate signal to the bionic client
and "man ps" to see when process is finished.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)