Bill Shupp wrote:
>
> on 8/1/01 10:48 AM, Ken Jones at [EMAIL PROTECTED] spake:
> > both are quick and dirty hacks to get it up and running. I agree.
>
> Yeah, I figure you probably already knew. But in case you didn't, I thought
> I'd mention it. ; )
>
> >> 2. Still doesn't restart qmail-send during vadddomain. Am I the only one
> >> with this problem? Seems to me that apache wouldn't allow it, so I imagine
> >> everyone would get the same thing. Perhaps I'm wrong... Anyway, I'm tempted
> >> to implement someone else's idea of creating a file like /tmp/restart-qmail
> >> when a domain is created. Then have an accompanying cron job to run every
> >> few minutes. If the file is there, restart qmail-send and delete the file.
> >>
> >
> > I think it is inside vpopmail. Bill, you are running supervise on your
> > qmail? Are you running vpopmail-4.10.30, i think the fix is in that
> > version. Not sure.
>
> No, I don't run supervise. Just the standard "csh -cf '/var/qmail/rc &'".
> And I'm running vpopmail 4.10.30 as well. Also apache 1.3.14.
>
> I posted a message to this list a while back about my findings, but here's a
> quick summary:
>
> Running the "r" script that comes with the source (as root), vadddomain (via
> vqadmin) successfully restarts qmail-send. However, if I use vqadmin via
> apache (running as nobody or qmails), qmail-send is NOT restarted. In the
> apache error log, I see this: "This /bin/ps is not secure for setuid
> operation." Incidentally, if I run the "r" script as a non root user, I get
> the same message to stderr.
Ah, /bin/ps is not secure. That must be apache holding up the show.
Stupid apache.
Ken
