there is some, for example, systemd triggered service in the basic distribution that depends on /var/log/messages rather than the journald mechanism, then yes it it a serious flaw.
No, sorry, I have very poor knowledge about how system log is worked. What i need is just a simple way to add application log to one file. My VPS use openSUSE 42.1, I deploy some application in it, with some self-defined boot start bash scripts, I want a simple way to write all application log to same file. start_some_application |logger I hope it logger output to one file which I familiar and commonly. the only I know from slackware is /var/log/messages. so, I don't know if some *service* is depend on /var/log/message. Thanks. Anton Aylward writes:
On 03/02/2016 02:19 AM, Per Jessen wrote:
Billy.Zheng(zw963) wrote:
Could you please tell me what version you use?
Why 42.1 can not find /var/log/messages ?
And, some service is not start correctly cause this file missing?
Install a syslog daemon, as Carlos suggested - syslog-ng or rsyslog, for instance.
+1
If there is a basic *service* that cannot start because of the absence of /var/log/message please tell us what it is.
I realise that there are going to be syslog scanning *applications* such as the venerable 'swatch' that are dependent on it, but that isn't a basic *service*.
If there is some, for example, systemd triggered service in the basic distribution that depends on /var/log/messages rather than the journald mechanism, then yes it it a serious flaw.
Please give details.
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon?
-- Geek, Rubyist, Emacser Homepage: http://zw963.github.io -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org