On Wed, 7 Nov 2018, [email protected] wrote:
Hi David,
I don't have privdrop configured. I'll add this later.
privdrop is more likely to cause problems that solve them
did the file already exist? or was it created by rsyslog?
Yes these existed before. This explains why it worked before.
I added this:
*.warning {
action(
type="omfile"
dirCreateMode="0750"
fileCreateMode="0640"
fileGroup="admin"
name="warnActionName"
file="/app/rsyslog/messages.all"
)
}
Next I stopped rsyslog, deleted the files, and started again, but no new file
was created.
rsyslog doesn't create files until there is a log that needs to go to them.
rsyslog doesn't change permissions of files that already exist, it only sets the
permissions of files that it is creating.
David Lang
_______________________________________________
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.
