Re: [syslog-ng]Changing Permissions on /dev/null
An utterly kludgy fix suggestion .... Instead of a /dev/null 'file' destination, have a 'program' destination which merely runs a script to call "cat >/dev/null", and leave sync() settings fairly big so that the pipe isn't flushed very often. Ted ************************************************************************************************ This E-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this E-mail message or attachments is strictly forbidden. If you have received this E-mail message in error, please contact the author and delete the message and any attachments from your computer. You are also advised that the views and opinions expressed in this E-mail message and any attachments are the author's own, and may not reflect the views and opinions of FLEXTECH Television Limited. ************************************************************************************************
On Wed, Feb 05, 2003 at 10:52:01AM +0000, Ted_Rule@flextech.co.uk wrote:
An utterly kludgy fix suggestion ....
Instead of a /dev/null 'file' destination, have a 'program' destination which merely runs a script to call "cat >/dev/null", and leave sync() settings fairly big so that the pipe isn't flushed very often.
syslog-ng can be taught not to clobber file permissions. either this way: destination d_thrash { file("/dev/null" perm(-1)); }; or options { perm(-1); }; (this last line will affect all file destinations) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Ted_Rule@flextech.co.uk