This is a PGP signed message sent according to RFC3156 [PGP/MIME]
--
In message
<Pine.GSO.4.10.10207101417080.3718-100000@???>,
Michael Collin Nielsen <michael@???> writes
>On Wed, 10 Jul 2002, Philip Hazel wrote:
>> On Wed, 10 Jul 2002, Michael Collin Nielsen wrote:
>>
>> > > . A pid file is not written when -oX is used to override the
>> > >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 :-)
>>
>> Er, the -oP option is supposed to do just that. If you give it -oP, it
>> will always write a pid file.
>
>Hmmm, I can't get it to write the pid-file when the process is started
>with the following options:
>
>/pack/exim-4.05/bin/exim -C /etc/eximmail/exim_outgoing.conf \
> -oP /var/spool/exim/exim-daemon.pid \
> -q30m
>
>I don't get a /var/spool/exim/exim-daemon.pid file :-/
Me neither.
Without one, I am unsure how to write the script to stop it. ( Excuse
any ignorance here, I am a newbie ).
>I've had a glance at the code,
[snip]
>Ie, if the exim proces is not a listening daemon, then a pid-file will
>never be written.
...
Regards
--
Dave English,
Client Software Development, Thus PLC,
Dorking Business Park, DORKING, Surrey, UK. RH4 1HJ
http://www.thus.net
--
[ Content of type application/pgp-signature deleted ]
--
