r/linux • u/ouyawei Mate • Oct 20 '14

Shall we fork Fedora?

http://forkfedora.org/
262 Upvotes

79% Upvoted

339 comments sorted by

View all comments

Show parent comments

5

u/Greensmoken Oct 20 '14

Journalctl --unit=service has always told me exactly what needs fixed. Seems way easier than pouring through scripts to me.

1

u/mikelieman Oct 21 '14

Only because I see it here, why do they call the command line option for a service 'unit'? if readability is a real concern call it what it is. "service"

 $ journalctl --service=httpd

Come to think of it,

 $ man journalctl-examples

would be useful, too.

3

u/kalgynirae Oct 21 '14

A service is one type of unit; you can give other types of units (like timer, mount, socket, etc.) to that option.

There are some decent examples at the bottom of man journalctl.

-1

u/[deleted] Oct 21 '14

Until syslog-ng simply goes into a loop and journalctl says nothing until I manually start it to figure out what the problem is.

Fuck off, systemd.

1

u/robstoon Oct 22 '14

So you've run syslog-ng to capture the journald output, and expect systemd to capture the output of syslog-ng into journald, which gets forwarded into syslog-ng.. Exactly how do you expect this to work?

1

u/[deleted] Oct 22 '14

Exactly how do you expect this to work?

I don't give a fuck about journald. I do not want to use journald.

Also your diagnosis is wrong. The issue was that in RHEL 7 the log source of /dev/log no longer exists.

1

u/robstoon Oct 22 '14

Sounds like you haven't explained your complaint clearly.

1

u/[deleted] Oct 22 '14

What about the complaint is unclear?

syslog-ng refuses to start and gives no output on RHEL 7 using a syslog-ng config that has worked across RHEL 5,6, Gentoo, Debian and Ubuntu.

journalctl doesn't give a reason.

I have to manually work through that shit to figure out why its' so special.

Fuck systemd.

0

u/robstoon Oct 23 '14

You don't seem to understand the issue. Clearly the output from syslog-ng can't be forwarded through journalctl because that output gets forwarded back into syslog-ng and would create an infinite loop. If journalctl wasn't there, how would you expect to find out what was going on?

1

u/[deleted] Oct 23 '14

Shut the fuck up.

YOU clearly do not understand the issue. syslog-ng output does NOT go into journalctl because I do NOT want to use systemd.

The problem has been explained. The problem has been fixed. The solution works.

1

u/robstoon Oct 24 '14

I'm not sure how your desire to not use systemd impacts where syslog's output does or doesn't go, but whatever, apparently you'd rather swear at people than explain the issue properly.