Return to Question

For a while looking for a solution that with systemd tools will give me an opportunity to bypass the journal and log directly to syslog. Potentially that can be also filtered, but only on journal not on syslog of course.

So far I can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append. This looks like not preferable since messages sent that way are raw with no identifier or timestamp that probably needs to be set by the sender (application) and this is out of my jurisdiction.

I know that I can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw these two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of them address specifically the above problem.

Can you point me to any other ideas on how to solve this problem?

For a while looking for a solution that with systemd tools will give me an opportunity to bypass the journal and log directly to syslog. Potentially that can be also filtered, but only on journal not on syslog of course.

So far I can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append.

Do not want to use above, since messages sent that way are raw with no identifier or timestamp that probably needs to be set by the sender (application) and this is out of my jurisdiction.

I know that I can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw these two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of them address specifically the above problem.

Can you point me to any other ideas on how to solve this problem?

For a while looking for solution that with systemd tools will give me opportunity to bypass journal and log directly to syslog. Potentially that can be also filter, but only on journal not on syslog of course.

So far can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append. This looks like not preferable, since messages sent that way are raw with no identifier or timestamp that probably need to be set by sender (application) and this is out of my jurisdiction.

I know that i can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw this two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of them address specifically above problem.

Can you point me any other idea how to solve this problem  ?

For a while looking for a solution that with systemd tools will give me an opportunity to bypass the journal and log directly to syslog. Potentially that can be also filtered, but only on journal not on syslog of course.

So far I can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append. This looks like not preferable since messages sent that way are raw with no identifier or timestamp that probably needs to be set by the sender (application) and this is out of my jurisdiction.

I know that I can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw these two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of them address specifically the above problem.

Can you point me to any other ideas on how to solve this problem?

For a while looking for solution that with systemd tools will give me opportunity to bypass journal and log directly to syslog. Potentially that can be also filter, but only on journal not on syslog of course.

So far can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append. This looks like not preferable, since messages sent that way are raw with no identifier or timestamp that probably need to be set by sender (application) and this is out of my jurisdiction.

I know that i can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw this two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of the address specifically above problem.

Can you point me any other idea how to solve this problem ?

For a while looking for solution that with systemd tools will give me opportunity to bypass journal and log directly to syslog. Potentially that can be also filter, but only on journal not on syslog of course.

So far can't make it right. My system is OL8 with systemd 239-68.

What was already tried:

[Service] ... StandardOutput=syslog StandardError=syslog SyslogIdentifier=my_service ... 

This gives dual logging to journal and to syslog. Second try was set StandardOutput and StandardError to append. This looks like not preferable, since messages sent that way are raw with no identifier or timestamp that probably need to be set by sender (application) and this is out of my jurisdiction.

I know that i can do it using ExecStart and 2>&1 with logger in separate script but really it is last resort since it is informal.

Also saw this two topics:

https://github.com/systemd/systemd/issues/6432

https://github.com/systemd/systemd/pull/24058

But none of them address specifically above problem.

Can you point me any other idea how to solve this problem ?