Ralf,
Thanks for the quick response.
> > So given all that, why am I not already logging to that log file?
> For unknown reasons (but I've already seen this once in the past)
> the ownership is incorrect: The file has to be
> -rw-r--r-- 1 cw cw 1393453 Oct 2 11:12 postfix.log
> So do a "chmod 644" and "chown cw" on this file, followed by a
> "/cw/etc/rc postfix stop start" and it should log fine.
I changed the file to..
-rw-r--r-- 1 cw cw 0 Sep 25 17:13 /cw/var/postfix/log/postfix.log
..but it still fails to acquire a single entry after a restart. I am
suspicious about only cw having write access. My understanding was that
the Postfix daemon(s) needed to be able to write directly to the log if
they weren't going through syslog (or fsl?).
I tried changing the owner of that log to "postfix", which is the Postfix
mail_owner in my configuration, but that made no difference.
Also of note is that postfix master messages are still going through
syslog:
Oct 2 10:09:47 cthulhu postfix/master[21013]: [ID 197553 mail.info] reload
configuration
> Keep in mind that just permissions 666 do not work because of security
> checks in Postfix.
Now I'm a bit (more) confused. How does Postfix know anything about this
log file? Isn't fsl acting as an intermediary of some kind?
>> The next question would be how do I use a different log file -
> Replace path="/cw/var/postfix/log/postfix.log" in /cw/etc/fsl/fsl.postfix
> with path="/var/log/maillog". Alternatively you can directly log to your
> syslogd(8) with the help of the fsl/l2 syslog channel.
As I suggested in my previous message I'd like to do it the "right" way,
which from Thomas's message was to..
...use the powerful functions of l2 and
get rid of your "real syslog" requirement
..which would be defining the log file in fsl.postfix, I presume.
Since nothing gets logged to /cw/var/postfix/log/postfix.log, I presume
that changing path in /cw/etc/fsl/fsl.openssh to /var/log/maillog won't
make any difference.
Thomas pointed out that there is a loop condition using the fsl-syslog
forwarding, so I expect that is not an option yet.
What do you suggest as the next step?
As for procmail...
> Because in OpenPKG's procmail pre-configuration mail (for
> multiple reasons ranging from backup reasons to multiple OpenPKG
> instance reasons, etc) is delivered to $HOME/.mail/inbox. If
> you it to be delivered to /var/mail/$LOGNAME you have to change
> /cw/etc/procmail/procmailrc and use:
> MAILDIR=/var/mail/$LOGNAME
> ORGMAIL=/var/mail/$LOGNAME
Bingo! That change had the desired effect. Thank you.
I only noticed $HOME/.mail/ mentioned in my user's procmail log for the
first time this morning. Since everything was working fine for me and I
was logging verbosely, I missed those lines in amongst the others. The
other user had a $HOME/.mail and was collecting his mail in there, though
we didn't know that.
-Andrew-
--
_________________________________________________________
| -Andrew J. Caines- 703-886-2689 Unix Systems Engineer |
| <[EMAIL PROTECTED]> WorldCom Web Hosting |
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
