Re: Logging daemon message in a specific file

2023-11-12 Thread Mik J
Hello Ze, Stuart, Thank you for your answers.Yes I did read the man page before sending my message but I understood "that further blocks would be evaluated cancelling !!prog" and therefore isakmpd and unbound would be logged in messages. At the end I didn't give a chance to this !*. Probably I'

Re: Logging daemon message in a specific file

2023-11-12 Thread Stuart Henderson
On 2023-11-12, Rosen Iliev wrote: > Hello, > > man syslog.conf is your friend. > > /!!prog/ causes the subsequent block to abort evaluation when a message > matches, ensuring that only a single set of actions is taken. /!*/ > can be used to ensure that

Re: Logging daemon message in a specific file

2023-11-12 Thread Zé Loff
On Sun, Nov 12, 2023 at 02:37:08AM +, Mik J wrote: > Hello, > I would like to log isakmpd and unbound messages in a specific file but I > don't want them to be logged in messages or daemon. > 1) With this first method, the messages are logged in their files but also in > messages and I don't

Re: Logging daemon message in a specific file

2023-11-11 Thread Rosen Iliev
Hello, man syslog.conf is your friend. /!!prog/ causes the subsequent block to abort evaluation when a message matches, ensuring that only a single set of actions is taken. /!*/ can be used to ensure that any ensuing blocks are further evaluated (i.e

Logging daemon message in a specific file

2023-11-11 Thread Mik J
Hello, I would like to log isakmpd and unbound messages in a specific file but I don't want them to be logged in messages or daemon. 1) With this first method, the messages are logged in their files but also in messages and I don't want them to be logged in messages: I find many queries and isak