Hello Jim,
The syslog-ng.conf specifies the user:group used for each destination (as well as permissions) Here is a quick example, but the manual is pretty comprehensive: #!# the main destination directory tree destination d_separatedbyhosts { file("/logs/syslog- ng/$HOST_FROM/$YEAR/$MONTH/$FACILITY.$PRIORITY.$YEAR.$MONT H.$DAY" owner("root") group("syslogng") perm(0640) dir_perm(0750) dir_group("sy slogng") create_dirs(yes)); };
The user and group used is entirely up to you based on how you want to grant access to these logs.
This settings doesn't work anyway. Indeed, I discover that is not a matter of local or non local file system. Infact, umounting the NFS file system from '/data/tmp-backup' I saw that the log isn't write anyway (even if the permissions are properly set to /data dir). I have solved (but I can't really figure out the cause - maybe it is the case to ask to Novell support) mounting the NFS file system under '/var/log/tmp-backup'. It is really strange for me, but I only can guess that some path are 'protected' by OS. If someone know something more about this strange behavior I will be happy to get this information.
My NFS comment is simply that if this is a central log server, I question why you would be using NFS mounted storage as opposed to local (direct attach or SAN) storage - but that is entirely up to you.
You are right but I need to take the file on a NAS server an I have no possibility to link it directly to the log host. Thanks, rocsca