Re: [rsyslog] How to completely move beyond Legacy Format?

[Rainer Gerhards]

2017-07-20 0:28 GMT+02:00 matthew.gaetano :
> Sorry i didn't really explain why we kept umask. As per documentation  we
> continue to add '$umask 000' at the top of the configuration file to prevent
> any possible issues with file creation. We did have issues early on when
> switching loggers where some inheritance permissions prevented omfile writes
> and queue/cache; that said i don't know that still occurs.

right. $umask is a global setting, not omfile related. I think we
missed moving it to scripting...

Rainer
>
> ~Regards
>
>
>
> -
> ~Regards
>
> Matthew Gaetano
> --
> View this message in context: 
> http://rsyslog-users.1305293.n2.nabble.com/How-to-completely-move-beyond-Legacy-Format-tp7592601p7592607.html
> Sent from the rsyslog-users mailing list archive at Nabble.com.
> ___
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T 
> LIKE THAT.
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Re: [rsyslog] How to completely move beyond Legacy Format?

[matthew.gaetano]

Sorry i didn't really explain why we kept umask. As per documentation  we
continue to add '$umask 000' at the top of the configuration file to prevent
any possible issues with file creation. We did have issues early on when
switching loggers where some inheritance permissions prevented omfile writes
and queue/cache; that said i don't know that still occurs.

~Regards



-
~Regards

Matthew Gaetano
--
View this message in context: 
http://rsyslog-users.1305293.n2.nabble.com/How-to-completely-move-beyond-Legacy-Format-tp7592601p7592607.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Re: [rsyslog] How to completely move beyond Legacy Format?

[David Lang]

I don't believe that umask works with the action() format, I think you need to 
specify file permissions in the action() call.


But as I said in another e-mail, there's no particular reason to be 'legacy 
free', there are some things that are simple and clearer in the legacy format 
than in a long action() statement, but if you have to setup parameters before 
the action statement, combining everything into one line with an action() 
statement is probably clearer.


simple filters and outputs are much easier to read in the legacy format.

David Lang

On Wed, 19 Jul 2017, matthew.gaetano wrote:


Date: Wed, 19 Jul 2017 10:03:07 -0700 (MST)
From: matthew.gaetano <matthew.gaet...@gmx.ca>
Reply-To: rsyslog-users <rsyslog@lists.adiscon.com>
To: rsyslog@lists.adiscon.com
Subject: Re: [rsyslog] How to completely move beyond Legacy Format?

To set global directives in version 8 you use the global configuration
object. http://www.rsyslog.com/doc/v8-stable/rainerscript/global.html

example:
global(
 workDirectory="/var/lib/rsyslog"
)


you can list more than one directive per global configuration object, but do
not set a global directive more than once.

AFAIK there is no non-legacy version of $IncludeCongfig, so one would
continue to use as is. It and umask are the only two legacy directives I
continue to use.

~Regards





-
~Regards

Matthew Gaetano
--
View this message in context: 
http://rsyslog-users.1305293.n2.nabble.com/How-to-completely-move-beyond-Legacy-Format-tp7592601p7592604.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.


___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Re: [rsyslog] How to completely move beyond Legacy Format?

[matthew.gaetano]

To set global directives in version 8 you use the global configuration
object. http://www.rsyslog.com/doc/v8-stable/rainerscript/global.html 

example:
global(
  workDirectory="/var/lib/rsyslog"
)


you can list more than one directive per global configuration object, but do
not set a global directive more than once.

AFAIK there is no non-legacy version of $IncludeCongfig, so one would
continue to use as is. It and umask are the only two legacy directives I
continue to use.

~Regards





-
~Regards

Matthew Gaetano
--
View this message in context: 
http://rsyslog-users.1305293.n2.nabble.com/How-to-completely-move-beyond-Legacy-Format-tp7592601p7592604.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.