On 07/17/2013 03:00 PM, drago01 wrote: > On Wed, Jul 17, 2013 at 2:57 PM, Denys Vlasenko <dvlasenk@xxxxxxxxxx> wrote: >> On 07/17/2013 02:45 PM, drago01 wrote: >>>>> instead of administrators simply adding rsyslog or syslog-ng manually >>>>> at install time or to their ks snippets. >>>> >>>> And this too was answered several times already. >>>> The machine in question may be already borked. >>>> Our support people will need to figure out - >>>> over the phone or email! - what has happened on client's >>>> installation, and having traditional grep/sed/awk >>>> recipes not working anymore because /var/log/messages >>>> is not there anymore is an extremely unwelcome discovery >>>> in an emergency. >>> >>> You can use grep / sed / awk on the jounrnal output as well. >> >> Please do read the text you are replying to. > > I did. Okay, I will try explaining with an example. A support engineer receives a panicked call from a customer. "Help, something wrong with our server!!!oneone". Engineer does not know what version of OS that server runs, what is installed there and how it is configured. So it needs to be investigated. Quite a typical situation. Engineer asks customer whether he has root login to the server. Customer has it. Then engineer asks to run "tail /var/log/messages". Customer says: "I see cannot open ‘/var/log/messages’: No such file or directory message". Great, isn't it? Engineer asks to run journalctl. Customer says: "I see 'Input/output error' message". -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
