I actually let syslog deal with it... something like this

/usr/lib/postgresql/8.4/bin/slon sql_cluster_master_slave  "dbname=master
user=navmap"| logger -t slony1

Syslog's logs are rotated automatically by logrotate.
You might want to set up a filter for "slony1" to stop slony cluttering 
up the main log file.

D

On 23/06/11 10:03, francescoboccacci at libero.it wrote:
> Hi to all,
> i have a question for you. I'n using slony to replicate two databases.
> I run cluster script, after:
>
> /usr/lib/postgresql/8.4/bin/slon sql_cluster_master_slave  "dbname=master
> user=navmap">  slonmaster.log&
> /usr/lib/postgresql/8.4/bin/slon sql_cluster_master_slave "dbname=slave
> user=navmap">  slonslave.log&
>
> at the end subscribe script.
>
> My question is:
>
> the two log file grow up in size day by day. I like to clean up these files
> and rebuild from scratch.
> Is there a slony command to do that or i have to create a script and run it
> from crontab that delete these files?
>
> Thanks
>
>
> Francesco
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general