[exim-dev] [Bug 309] An init.d script for exim is needed

Top Page
Delete this message
Reply to this message
Author: Phil Pennock
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 309] An init.d script for exim is needed
------- You are receiving this mail because: -------
You are the QA contact for the bug.

http://bugs.exim.org/show_bug.cgi?id=309

Phil Pennock <exim-dev@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |exim-dev@???
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX





--- Comment #2 from Phil Pennock <exim-dev@???> 2008-08-13 05:32:20 ---
Different operating systems handle init scripts in wildly different ways. Some
have start-stop-daemon, some don't; some have policies on different return
codes. Some expect to be able to handle faststart in addition to start.

And then each OS comes along and decides to refactor some aspect and change all
their init scripts to a new standard.

Generally, OS packagers do a good job of providing the relevant init scripts
for their platform. It's a good division of labour and if Exim starts shipping
scripts, some users will start using Exim's instead of the OS-specific script
and that will just create headaches for the OS maintainers.

Further, integrating Exim can involve rather more than just an init script.
Eg, some systems use mailwrapper(5) and expect mailer.conf(5) to be edited.

Anyone "rolling their own" is generally capable of providing their own init
script for their OS, or cribbing from a script already available.

If anyone thinks that there's a reasonable solution to this wishlist item,
please re-open the bug explaining what the solution is, which OSes it works on
and other relevant information.

In the meantime, marking WONTFIX as a substitute for INFEASIBLE.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email