On Wed, 2005-11-30 at 16:46 -0500, Sven Willenberger wrote:
> I have had an issue with logging slony for the last release or so.
> Currently I am using 1.1.2 on FreeBSD 6.0 and PostgreSQL 8.0.4. There
> are 2 different ways I can start up the slon daemon and get logging but
> what appears to be happening in the background is vastly different
> between the two.
> 
> Method 1: The daemon gets started as follows:
> 
> cd /usr/local/etc/slony
> /usr/local/bin/slon -p /var/run/slon/slon.pid -d 1 T1 'dbname=mydb
> user=myuser' | /usr/local/sbin/rotatelogs slony.%a.log 86400 &
> 
<snip>
> 
> every 10 minutes or so a cleanupEvent() and delete logs occur.
> 
> Method 2:
> 
> using the FreeBSD rc system slon is started as 
> /usr/local/bin/slon -f /usr/local/etc/slon.conf -p /var/run/slon.pid
> 
> Where slon.conf contains:
> syslog 2
> syslog_facility 'LOCAL1'
> log_level 1
> log_timestamp 0
> pid_file '/var/run/slon.pid'
> 
> cluster_name T1
> conn_info 'dbname=mydb user=myuser host=localhost port=5432'
> 
> I have LOCAL1 set to log to /var/log/slony.log
> 
<snip>
> 
> And so on, each 10 minute cycle it would appear another helper thread is
> created as evidenced by the ever growing pair of cleanupEvent() and
> delete logs with each cycle. Any ideas as to a) what may be causing this
> and b) how to troubleshoot what is going on here?
> 
> Sven
> 
> _______________________________________________

No ideas on this one? Nobody else experiences this? No troublshooting
tips? This seems rather broke and I cannot figure out if it is OS
specific or even my particular setup specific.

Sven