[syslog-ng]hosts... today's stupid question :}

[bretwatson@charteredsemi.com]

Hi Bazsi,
but it is listed as a valid macro and digging through the code it is
actually there as in the macroexpansion proc...

does that mean not all macro identifiers are currently being expanded?
Which ones are valid?

Cheers

Bret





Balazs Scheidler <bazsi@balabit.hu>      10/04/2002 05:26
Sent by: syslog-ng-admin@lists.balabit.hu

Please respond to syslog-ng
                                                                               
             To: syslog-ng@lists.balabit.hu                                    
             cc: (bcc: WATSON Bret/IT/CHRT/ST Group)                           
             Subject: Re: [syslog-ng]hosts... today's                          
             stupid question :}                                                
                                                                               
                                                                               
                                                                               






On Wed, Apr 10, 2002 at 08:22:26AM +0800, bretwatson@charteredsemi.com
wrote:
>
> Hi All,
> a stupid question most probably,
> I'd like to build a generic destination for my default filter so that any
> new hosts get dropped into their own directory
>
> something like
> destination host { file("/usr/log1/$HOST/$YEAR$MONTH$DAY" owner(root)
> group(logusers) perm(0640) dir_perm(0755)); };
>
> But syslog-ng doesn't seem to like it and complains of syntax errors all
> the time..

host is a reserved word, don't use it for identifiers. the best bet is to
prefix identifiers with the purpose, e.g. d_host for destination f_host for
filters and so on. It will not collide with reserved words then.

--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C
8EB1

_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng





[This e-mail is confidential and may also be privileged. If you are not the
intended recipient, please delete it and notify us immediately; you should
not copy or use it for any purpose, nor disclose its contents to any other
person. Thank you.]