Exit with err 8 if pid file not writable after forking.

This commit is contained in:
Radim Kolar 2020-06-05 20:04:33 +02:00
parent 0cc86455da
commit bec9c41478
2 changed files with 2 additions and 1 deletions

View File

@ -10,6 +10,7 @@ Version NEXT
make sure that our descriptor for running in inetd is not 0 to 2, make sure that our descriptor for running in inetd is not 0 to 2,
because we closing these later. This should help systemd internal because we closing these later. This should help systemd internal
inetd to work correctly using fspd socket activation. inetd to work correctly using fspd socket activation.
fspd exits with err 8 if can't write pidfile after forking
Version 2.8.1b29 - 24 Aug 2019 Version 2.8.1b29 - 24 Aug 2019
added scons command line argument without-fspscan=yes for building added scons command line argument without-fspscan=yes for building

View File

@ -374,7 +374,7 @@ int main (int argc, char ** argv)
if (forkpid == 0) { /* child prozess */ if (forkpid == 0) { /* child prozess */
if (pidfile(pidlogname)) { if (pidfile(pidlogname)) {
pidfile_cleanup(pidlogname); /* try cleanup */ pidfile_cleanup(pidlogname); /* try cleanup */
exit(1);/* cannot write pid file - exit */ exit(8);/* cannot write pid file - exit */
} }
} else if (forkpid > 0) { /* father prozess */ } else if (forkpid > 0) { /* father prozess */
_exit(0); _exit(0);