Have you tried the "copytruncate" option in logrotate.conf ? I am using it without any problems on Solaris8. ++++++++++++++++++++ copytruncate Truncate the original log file in place after creating a copy, instead of moving the old log file and option- ally creating a new one, It can be used when some pro- gram can not be told to close its logfile and thus might continue writing (appending) to the previous log file forever. Note that there is a very small time slice between copying the file and truncating it, so some logging data might be lost. When this option is used, the create option will have no effect, as the old log file stays in place. +++++++++++++++++++++++ Regards \\ Naman

My pb : before the log rotate, all is good. After logrotate, syslog-ng don't write in the remote file.