okay, I figured it out. If the journalctl doesn't run neither rsyslog nor journalctl (last one is obvious) don't get anything.
after I started the journalctl the logger output appeared in journalclt and tail /var/log/messages output. Balint On Thu, 2014-09-11 at 19:04 +0100, Balint Szigeti wrote: > hello > > today I installed the rsyslog and enable it then disabled (then > masked) systemd-journal-flush, systemd-journald services. Plus I > disabled systemd-journald.socket as well. > It broke my system. After I closed the sudo session I could gain root > access plus I couldn't start any program only forks for the existed > ones (like gnome terminal). > The reboot didn't work. The box just didn't start up. :( (just remark > - systemd is not depends on itself........) > > I booted into runlevel 1 (yeeeah - runlevel doesn't exist on systemd - > I wanted to say rescue.target) and redo the mask and enable > everything. > > I've noticed the rsyslog doesn't listen to the system logging. > > I've run logger command but I don't find it in the log. I've checked > the journalctl and /var/log/messages file as well. > > # logger -t AAAA hello > # journalctl |grep hello > # grep hello /var/log/messages > # > > Does anyone have a clue?
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
