Bug 24923 - /etc/init.d/xmail does not run
|
Bug#:
24923
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: nick@capital-internet.net
|
Reported By: seriv@parkheights.dyndns.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: /etc/init.d/xmail does not run
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2003-07-20 15:38 0000
|
The same thing as in bug 24620: since lines end with <CR>/<LF> I got "bad
interpreter"
trying to start XMail.
The same about file files/xmail.confd. Should I enter this as a separate bug?
Sergey
I am sorry, but file files/15xmail also has line ending <CR><LF> and this
prevents XMail server from starting.
Sergey Ivanov
xmail-1.16 is now in portage. files/* have the cr-lf stuff removed. Also
xmailwizard is now executable. Please test.
Thank you, I have synced to xmail-1.16 and tested.
/etc/init.d/xmail does not start. It says:
===
# /etc/init.d/xmail start
* Starting XMail...
xargs: environment is too large for exec
===
I have not managed with xargs, so I propose patch for files/xmail.initd eliminating xargs call
(From update of attachment 14872 [details])
>--- /usr/portage/net-mail/xmail/files/xmail.initd 2003-07-21 03:40:20.000000000 -0400
>+++ /usr/local/portage/net-mail/xmail/files/xmail.initd 2003-07-22 07:52:56.000000000 -0400
>@@ -60,19 +60,17 @@
>
> if [ ! -c ${CHROOT}/dev/null ]
> then
>+ mknod ${CHROOT}/dev/null c `\
> ls -Ll /dev/null |\
>- awk '{print sub(",","",$5) " " $6}' |\
>- xargs mknod ${CHROOT}/dev/null c
>+ awk '{print sub(",","",$5) " " $6}'`
> fi
>
> chown -R xmail.xmail ${CHROOT}
>
> cp -R -u /etc/xmail/* ${CHROOT}${MAIL_ROOT}
>
>- cd ${CHROOT}
>- ldd var/MailRoot/bin/XMail |\
>- sed -n 's/[[:blank:]][^>]\+>[[:blank:]]\([[:graph:]]\+\).*/\1 lib\/ /p'\
>- |xargs -n 2 cp -u
>+ cp `ldd ${CHROOT}${MAIL_ROOT}/bin/XMail |\
>+ sed -n 's/[[:blank:]]*[^=]*=>\([^(]*\).*/\1/p'` ${CHROOT}/lib/
> start-stop-daemon --start -c xmail -r ${CHROOT} \
> --startas ${MAIL_EXEC} --pidfile=${MAIL_PID} -- \
> ${MAIL_CMD_LINE}
Also, please, change order of lines
chown -R xmail.xmail ${CHROOT}
and
cp -R -u /etc/xmail/* ${CHROOT}${MAIL_ROOT}
in files/xmail.initd, otherwise it takes two or three attempts to chown all necessary for XMail files.
Sergey
And the last correction from bug 15931, XMail SMTP needs /tmp in it's chrooted
jail, so line
===
for subdir in dev lib var/run var/MailRoot
===
should be changed to
===
for subdir in dev lib var/run var/MailRoot tmp
===
Sergey
Hi,
this bug has status "resolved" and resolution "fixed" but this is not the real status! /etc/init.d/xmail as it is in portage can not be used! It "runs" but does not "works". It does not start XMail server!
What should I do? Should I open new bug?
Sergey
I have updated the initd file with your changes. I haven't changed the CTRL
port though as there shouldn't be a problem with that port. Please test.
I also added a warning in postinst so that users are sure to have iptables
enabled in their kernels before they expect things to work.
xmail-1.16 appears to work good :)