Add new comment

Submitted by JoachimDurchholz (registered user) on Mon, 2007-03-12 16:10.

At least in Debian-based distros (like Ubuntu), changes for service foo should go into /etc/default/foo, not directly to /etc/init.d/foo. In this case, the PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid" option should go to /etc/default/saslauthd, where it will override the PIDFILE setting from /etc/init.d/saslauthd. Background: /etc/default/saslauthd is a "conffile"; changes in it won't be touched by updates. /etc/init.d/saslauthd is not a conffile and may be overwritten by the next update.

Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.

Reply

*
*
The content of this field is kept private and will not be shown publicly.


*

  • Images can be added to this post.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <div>
  • Lines and paragraphs break automatically.