Am 18.05.2016 um 16:23 schrieb Pradeepa Kumar:
I have a script in ExecStop in service file. In journalctl, The time difference between "Stopping XYZ service " and logs from my script in ExecStop is 42 sec. Does that mean systemd itself took long time to start stopping of service?
no, it means systemd is only the messenger and your script took 42 seconds to finish
On Wed, May 18, 2016 at 5:36 PM, Lennart Poettering <lenn...@poettering.net <mailto:lenn...@poettering.net>> wrote: On Wed, 18.05.16 16:00, Pradeepa Kumar (cdprade...@gmail.com <mailto:cdprade...@gmail.com>) wrote: > Hi experts, > I am using systemd v219. > I need help with a systemd issue that I am seeing. > I see that some times stopping of service is taking long time (42 sec). > i checked this in journal logs also. > is this is known issue ? > how do i debug this ? > and any solutions ? Well, that depends on the specific service. If a specific service takes 42s to shut down, then try figuring out what it does. If there's nothing in the journal, then maybe the service maintains its own logs? If it does not, see if you can turn on debug logging for it. Either way, that's really a question to ask the maintainers of that service, not to systemd upstream.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
