This is a PGP signed message sent according to RFC3156 [PGP/MIME]
--
In message <20020710192333.GA21993@???>, Simon Williams
<simon@???> writes
>* On Wed, Jul 10, 2002 at 02:53:08PM BST, Dave English
><davide@???> wrote:
>> 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
>> >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 ).
>
>It appears to me that, if you didn't specify the location of the pid
>file in the Makefile when you compiled, then it will be called
>exim-daemon.pid and be in the Exim spool directory (wherever that is
>in your installation).
But you don't get a .pid file if it is not a demon, that is the point.
When I run with -bd then a .pid file is created - either at the path
that I set in the Makefile or the one that I specified a the -oP. But
without a -bd, for the deliver only queue runner, no .pid file is
created whether I use a -oP or not.
Now Philip will fix that in the next minor release, but I was just
wondering what I could do in the meantime - apart from killing them by
hand, that is.
>It should be a plain text file with a number, indicating Exim's
>process ID, followed by a line feed.
>
>To find it, you could try:
>
>locate exim-daemon.pid
>
>or look in the Makefile to see if its location was explicitly defined.
>
>A script to kill Exim could simply contain:
>
>kill `cat /path/to/pid-file`
>
>or
>
>kill $(cat /path/to/pid-file)
Thanks anyway
--
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 ]
--
