Your message dated Wed, 16 Apr 2008 17:40:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line exim has been removed from Debian, closing #146012
has caused the Debian Bug report #146012,
regarding exim 3.35-1 initscript
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
146012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146012
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.35-1
When running exim as a standallone-daemon, and not from inetd, the
initscript dont saves a pid under /var/run/exim/exim.pid on start, and so the
initscript can't stop the daemon.
# ls /var/run/exim/
# /etc/init.d/exim start
Starting MTA: exim.
# ls /var/run/exim/
exim.pid-bd
???????????
the only thing I changed in the intscript, is deleting -q30m, as I want to
run the delivery after fetching mail in a crond-script.
In fact, there should be a variable in the script, to set the wanted
exim-options
the line in question looks now like this:
start-stop-daemon --start --pidfile /var/run/exim/exim.pid --exec $DAEMON --
-bd;
how this d... '-bd' gets appendet to the pid-file:
man exim:
...
If a daemon is run with only one of -bd and
-q<time>, then that option is added on to the end of the file name
...
a sort of solution is to append '-bd' on stop and reload, but its not a good
one. Another one may bee to append -ql instead of -q30m.
If anyone knows a better solution, please let me know.
Klaus Zerwes
--- End Message ---
--- Begin Message ---
Version: 3.36-18.2+rm
The exim package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/420191 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Barry deFreese
--- End Message ---
