On Tue, Jan 01, 2002 at 05:58:09PM -0500, Sam Varshavchik wrote:
>
> 23981 read(3, "[EMAIL PROTECTED]\nUID=100"..., 8191) = 119
>
> ...
>
> 23981 chdir("/mail/karmak.org/test") = 0
>
> That's a succesfull authentication followed by opening
> /mail/karmak.org/test as the account's home directory. However, the next
> call is:
> execve("/pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/bin/imapd"
> , ...
> Based on the subsequent trace, this file appears not to be the imapd server
> binary, but the system startup imapd script. So, something is seriously
> screwed up here. Unfortunately, it is not possible to determine what that
> "something" is. That's because this pathname suggests that you did not
> compile and install Courier yourself, but used a prepackaged version. You
> should contact the package's maintainer for additional assistance. I have
> no idea how your package was built, or what custom configuration this
> package uses. Unless you want to tell us that you ran the configure script
> yourself (followed by make install), nobody will have any idea what your
> environment is.
You've hit it! Yes, I compiled and installed this myself, and bin/imapd
IS a symlink to the imapd startup script. I've posted the complete build
log to:
http://karmak.org/2002/01/courier/i686-pc-linux-gnu.1.log
It's big (~1MB), but it's all there, from 'configure' to 'make install'.
Commands I've issued are prefixed with "@@" to find them easily, and
the very beginning of the log shows the environment variables that are
set.
If you do a search for "bin/imapd", you'll notice that during the
installation the following two commands are run (this appears ~90% into
the log):
rm -f /pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/bin/imapd
ln -s /pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/share/imapd
/pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/bin/imapd
It would appear that the original bin/imapd gets deliberately removed
during 'make install', and replaced by a symlink to the imapd startup
script.
This actually happens to _several_ of the files in the bin directory,
including the pop3 binary. I thought all those symlinks looked a little
strange, but since everything else was working fine, I assumed that, for
whatever reason, that was just the way things were done. Note that
bin/pop3d and bin/pop3d-ssl are ALSO symlinks to startup scripts, just
like bin/imapd, but POP3 works fine. For this reason it didn't occur
to me that the installation was bad. Seriously, despite all those
crazy symlinks, the rest of Courier exhibits no end-user problems
at all.
Glad you spotted this. I'm digging into the problem right now, but I
thought I'd share the news and post the link to the log file in case
you or someone else wanted to see it also.
Thanks so much.
m.
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
