[syslog-ng] messed up permissions on /dev/null destination on solaris

[Ed Ravin]

On Tue, Oct 18, 2005 at 05:14:05PM +0200, Balazs Scheidler wrote:
> On Mon, 2005-10-17 at 09:18 -0700, Nate Campi wrote:
> > On Mon, Oct 17, 2005 at 11:57:37AM -0400, Ed Ravin wrote:
> > > But let's go one level deeper - why are the "operators" configuring
> > > syslog-ng.conf to write to /dev/null in the first place and thus
> > > making this error?  It's because the sysadmins want to discard
> > > certain log entries.  Why not facilitate that by making a special
> > > "discard" destination?
...
> you can create a destination which has no drivers, e.g. this is valid
> and works as expected:
> 
> destination d_null {};
> 
> log { source(s_local); destination(d_null); };

Is this documented anywhere?  I would have used this a couple of years
ago had I known about it.  Even so, it would still be good to have a
"discard" keyword for readability of the config file and an easy way
to learn about the feature when reading the man page (i.e. how do you
look up a "null" keyword?).