On Wed, 10 Jul 2002, Philip Hazel wrote:
> On Wed, 10 Jul 2002, Michael Collin Nielsen wrote:
>
> > However the other exim proces, that does the delevery, is started using:
> > /pack/exim-4.05/bin/exim -C /etc/eximmail/exim_outgoing.conf -q30m
> >
> > Using this setup only the first exim proces creates a pid-file (in
>
> Exim 3 tried to be clever with daemon pids, and got itself into a
> tangle. I made things much simpler in Exim 4.
>
> > Is this a bug or a feature or can I give exim som option that forces it
>
> Feature.
Ofcourse :-)
> > "When a listening daemon is started without the use of -oX (that is,
> > without overriding the normal configuration), it writes its process id to
> > a file called exim-daemon.pid in Exim's spool directory."
> >
> > That might give me a clue as to why the file is not created, however I
> > really would like to have it :-)
> >
> > Any advice ?
>
> Read the NewStuff file as well as the manual. :-) The following change
> was made for Exim 4.01:
>
> 2. There is a new command line option -oP which allows the pid file path to
> be specified on the command line. The rules for deciding whether an Exim
> daemon should write a pid file have been changed and are now as follows:
>
> . A pid file is not written unless the -bd option is used (that is, daemons
> created with -q that don't do SMTP listening are esoteric beasts that
> don't count).
>
> . A pid file is not written when -oX is used to override the SMTP port or
> the interfaces, unless -oP is used to specify a path explicitly.
>
> (I'll be updating the manual for the next release.)
Thanks, that explains why I can't get exim to create the pid-file.
Wouldn't it be useful to have an option that tells exim to write the
pid-file disregarding the rules you outlined ? Well... I would find it
very usefull :-)
Regards
-Michael
--
Michael Collin Nielsen mailto:michael@hum.auc.dk
M.Sc.E.E. http://www.hum.auc.dk/~michael
Sysadm in Faculty of Humanities, Aalborg University
