Pidfiles are hardcoded to /var/run/dbmail-<whatever>.pid, with -p specifying
an alternative file of your choosing. It is currently a fatal error if a pid
file cannot be created, and it is also a fatal error if the pidfile already
exists and contains a valid pid:
Jul 9 02:57:51 cubit dbmail/pop3d[27138]: pidfile.c, pidfile_create: Cannot
open pidfile [/var/run/dbmail-pop3d], error was [Permission denied]
I've finished pop3d. Doing imapd, lmtpd, timsieved will be a cinch. At that
point, everyone will have been migrated to getopt, too. Here's the output:
[EMAIL PROTECTED] dbmail-working-2004-07-03]$ ./dbmail-pop3d -h
*** dbmail-pop3d ***
This daemon provides Post Office Protocol v3 services.
See the man page for more info.
Common options for all DBMail daemons:
-f file specify an alternative config file
-p file specify an alternative runtime pidfile
-n do not daemonize (no children are forked)
-v log to the console (only useful with -n)
-V show the version
-h show this help message
[EMAIL PROTECTED] dbmail-working-2004-07-03]$ ./dbmail-pop3d -n -p this.pid -V
*** DBMAIL: dbmail-pop3d version $Revision: 1.109 $ (c) 1999-2004 IC&S, The
Netherlands
[EMAIL PROTECTED] dbmail-working-2004-07-03]$ ./dbmail-pop3d -n -p this.pid
[EMAIL PROTECTED] dbmail-working-2004-07-03]$ cat this.pid
27151
