Am 08.03.2016 um 01:54 schrieb J dreadpiratejeff@gmail.com [LINUX_Newbies]:
>
>
> On Sunday, March 6, 2016, Scott scottro@nyc.rr.com
> <mailto:scottro@nyc.rr.com> [LINUX_Newbies]
> <LINUX_Newbies@yahoogroups.com <mailto:LINUX_Newbies@yahoogroups.com>>
> wrote:
>
>
> Yes, in /var/log
>
> You might want to try messages, that is, /var/log/messages.
>
> If there's no /var/log/messages it is probaby using systemd, in
> which case,
> you have to run journalctl
>
>
> It may be called syslog also.
>
***
Do You talk about the directory or journalctl?
> But if it's a hardware problem like failing RAM here will be no
> indication in logs anywhere (except for the firmware System Event Log
> which may or may not be useful)
>
*
I m sure its a software problem.
>
>
> https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
>
> gives some information.
>
Thank You Sophie
Posted by: "highskywhy@yahoo.de" <highskywhy@yahoo.de>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
No comments:
Post a Comment