Found it!

First I created ./dev/log using 'cp -a /dev/log /var/amavisd/dev/log'

Then I had to add 'unix-stream("/var/amavisd/dev/log");' into
syslog-ng.conf as a source.

It had nothing to do with /etc/rc.conf.  :)

Thanks for leading me in the right direction!!!

-Mark 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Martinec
Sent: Tuesday, February 28, 2006 10:21 AM
To: [email protected]
Subject: Re: [AMaViS-user] Amavid-New in chroot.

Mark A Jenks,

> I'm running a Gentoo box running Amavisd-new 2.3.3-r2.
> I've been running it in chroot, but have since removed it from there 
> since Logging to mail.log/mail.info is not working.
> I am running syslog-ng 1.6.8.
> I'm not sure what changed, but somewhere around the update from about
> 2.1 it stopped working.

amavisd-new-2.3.2 release notes

INCOMPATIBILITY with 2.3.1 and earlier versions:

If running amavisd daemon in chroot please note:

  Each child process now opens its own syslog connection or a file
descriptor
  to a log file, and no longer inherits a connection from its parent.
  When running in chroot jail and logging to syslog, the syslog client
  routines need syslogd socket to be present in the chroot subtree to be
  able to establish a connection with syslogd, otherwise logging output
  may be lost. Additional syslogd sockets (to be made available in the
  jail) may be requested from the syslogd daemon, see its documentation.
  This requirement is equivalent to the requirement of chrooted Postfix
  services (see Postfix documentation file BASIC_CONFIGURATION_README).
...
- reopen log file or syslog connection in each child process to make it
use
  its own file descriptor; also minimizes transients when syslogd is
restarted
  and its socket re-created, as reported by Les Ault. When running in
chroot
  please make sure a syslogd socket is also available in the chroot
jail,
  see README.chroot for syslogd options (and BASIC_CONFIGURATION_README
  in Postfix documentation for the Postfix equivalent);


README_FILES/README.chroot
...
Logging should preferably be directed to syslog. Configure syslogd to
provide a socket in the amavis jail (option -l on FreeBSD, option -a on
OpenBSD and Linux). Under FreeBSD place something like:
  syslogd_flags="-l /var/amavis/var/run/log -ss"
into /etc/rc.conf .


  Mark


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language that extends applications into web and mobile media. Attend the
live webcast and join the prime developer group breaking into this new
coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to