Jay Cornwall <[EMAIL PROTECTED]> tapota : > Hi > > I've got a partially working Savane installation set up now, and I'm > just finishing up mailing list integration with Mailman. > > It seems that when a list is created, the script sv_mailman is > executed at regular intervals by cron to actually create the list. A > look at the provided etc/crontab entry shows: > > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin: > > This should correctly find my Mailman executables, symlinked into > /usr/local/bin. However the script sv_mailman (and I guess maybe > several others) are using hard-coded paths to /usr/sbin/newlist > etc. in order to execute the Mailman commands. This fails for obvious > reasons, but doesn't even log as a failure in the script. (it took a > while to find the cause because of this) > > Is there any need for the paths to be hard-coded, given the > environment is set correctly in the crontab? Even basic assumptions > like /usr/bin/mail fail, because RHEL 3.0 only has /bin/mail.
Hello, Hum, in fact, the advantage of it is the fact that it does work even with a $PATH that do not include /usr/sbin (and cron may not be the only situation where we run the script). However, the hardcoded paths are debian's ones and there is no way to be sure other distros got the same paths. So I guess you are right and we should only rely on $PATH, and print a meaningful error message when the binaries haven't been found in the $PATH. It is just a matter of doing it now. Regards, -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+
