| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: wrapper-script & Unable to run qmail-remote |
| From: | Harald Hanche-Olsen <hanche@math.ntnu.no> |
| Date: | Fri, 13 Apr 2007 08:30:38 +0200 (CEST) |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <20070413005546.GI16394@aleut.local> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <20070413005546.GI16394@aleut.local> |
+ Kyle Wheeler <kyle-qmail@memoryhole.net>: | -rwx–x–x 1 root root 724 2007-04-12 18:31 qmail-remote* | -rwx–x–x 1 root root 296K 2007-04-12 17:01 qmail-remote.orig* | -rwx–x–x 1 root root 724 2007-04-12 18:29 qmail-remote.sh* | | It won't even do: | | #!/bin/sh | exec /var/qmail/bin/qmail-remote "$@" That would seem to result in an infinite exec() loop. Surely, you intended to run qmail-remote.orig, right? Also, from a quick look at qmail-rspawn.c, you would also get the "Unable to run ..." message if qmail-rspawn failed to set up file descriptors for qmail-remote. Not that this is a likely cause of your problem, but a possibility worth eliminating. You may need to do some syscall tracing to find out what is going on. - Harald |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: wrapper-script & Unable to run qmail-remote, Kyle Wheeler |
|---|---|
| Next by Date: | Re: setting up client relay-only smtpd, Charles Cazabon |
| Previous by Thread: | Re: wrapper-script & Unable to run qmail-remote, Kyle Wheeler |
| Next by Thread: | Re: wrapper-script & Unable to run qmail-remote, Kyle Wheeler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |