Bug 46195

Summary:	Service Configuration - PIDFile Option Notice
Product:	systemd	Reporter:	danielodev
Component:	general	Assignee:	Lennart Poettering <lennart>
Status:	RESOLVED INVALID	QA Contact:
Severity:	minor
Priority:	medium
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description danielodev 2012-02-16 13:27:07 UTC

When setting up a service configuration file and the 'Type' is set to 'forking' and the 'PIDFile' option is set but not pointing to the right place systemctl directs output to the terminal but does not log any notices anywhere. When you terminate (ctrl-c) it then kills the service you are trying to start.

I was expecting that if the PID file didn't exist or was empty that the GuessMainPID would still be set to true and try to guess the PID. I at least expect for the service to still start in the background and to get some sort of notice but I didn't see one anywhere.

It would be really nice if there was a notice that the PID file didn't exist or was empty and systemd tried to guess the PID anyway.

Comment 1 Lennart Poettering 2014-06-23 09:41:03 UTC

Hmm, this one doesn't make sense to me. systemctl never directs output of services to the terminal, we don't support that at all, services always run entirely detached from the session you start them from and hence have no access to your terminal. Also, C-c on systemctl start will just abort the systemctl process waiting for a job, but not the job itself.

So I am not sure I really understand what the bug is about. I also believe that the current behaviour is pretty good, also regarding pid files being written incorrectly or too late. Hence closing. If there's a bug left please open a new bug!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.