Hi,

I’ve asked the question about some strange result when running

syslog-ng-1.6.0rc3 on coosbay server.

Syslog-ng couldn’t create log files, but generate wild files in current

work directory.

--sample config file—

# Simple syslog-ng.conf file.

options {use_fqdn(no);sync(0);};

source s_sys { unix-stream("/dev/log"); internal(); };

destination d_security { file("/usr/local/var/log/security" create_dirs(yes)); };

destination d_messages { file("/usr/local/var/log/messages" create_dirs(yes)); };

destination d_console { usertty("root"); };

filter f_authpriv { facility(auth, authpriv); };

filter f_messages { level(info .. emerg)

and not facility(auth, authpriv); };

filter f_emergency { level(emerg); };

log { source(s_sys); filter(f_authpriv); destination(d_security); };

log { source(s_sys); filter(f_messages); destination(d_messages); };

log { source(s_sys); filter(f_emergency); destination(d_console); };

--end—

[root@power sbin]#./syslog-ng

[root@power sbin]# ls

? stunnel syslog-ng …

[root@power sbin]# cat ?

Sep 27 13:53:56 s_sys@power syslog-ng[28098]: syslog-ng version 1.6.0rc3 starting

Any idea on why this file is created but normal log files fail to be exist?

Thanks

zhen