Well, I figure if it's not meant to be run suexec, I shouldn't. So, I've
recompiled apache sans suexec support (and removed the old suexec binary)...
Also went ahead and recompiled qmailadmin. So, any suggestions for a
non-suexec environment?
jesse
-----Original Message-----
From: Peter Bieringer [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 09, 2000 3:46 AM
To: Jesse Peterson; '[EMAIL PROTECTED]'
Subject: Re: 'bad file' error after login
At 17:25 08.09.2000 -0400, Jesse Peterson wrote:
>Hi all. I browsed through the archives and saw a few people had had this
>problem, but didn't see any mention of a fix, so my apologies if this is a
>repost.
>I just installed qmailadmin .35 and apache 1.3.12. My qmail/vpopmail/mysql
>system is functioning ok. The qmailadmin build appeared to go without a
>hitch.
>However, after I enter l/p/d, I get a page that simply says 'bad file'.
>
>I rebuilt apache with suexec support (wasn't actually sure if it needed
that
>or not...), but all other default options.
>The perms on the qmailadmin cgi:
>-rwsr-sr-x 1 vpopmail vchkpw 84204 Sep 8 16:25 qmailadmin
>
>any suggestions or help would be greatly appreciated!
Look in the /var/log/httpd/suexec_log. Normally, if the virtual server is
configured for suexec, SUID/SGID isn't allowed anymore. Also user/group
entries for the virtual server must match executable and directory.
Peter
