Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33357 - [syslog-ng] Replace with journald

Attached to Project: Arch Linux
Opened by جاك الفضة (jacksilver) - Thursday, 10 January 2013, 11:40 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 10 January 2013, 14:36 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Syslog-ng should be replaced with systemd's journald as the default process for system logging.

Advantage :

Systemd's journald is a system journaling service to collect and store logging data. The journals are indexed and logs messages in a secure manner. Systemd secures logs with a new process it calls forward secure sealing.
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 10 January 2013, 14:36 GMT
Reason for closing:  Not a bug
Additional comments about closing:  journald is already the default.
Comment by Dave Reisner (falconindy) - Thursday, 10 January 2013, 13:19 GMT
syslog-ng is in extra, so there's nothing that syslog-ng does "by default" unless the user explicitly install it. What exactly are you asking for here?
Comment by جاك الفضة (jacksilver) - Thursday, 10 January 2013, 13:59 GMT
Make journald the default logger on new install. We should do not need syslog-ng or rsyslog at all on a new install.
Comment by Dave Reisner (falconindy) - Thursday, 10 January 2013, 14:10 GMT
> Make journald the default logger on new install.
Yes, systemd is installed by default. The journal is a requirement for systemd.

> We should do not need syslog-ng or rsyslog at all on a new install.
And again, these aren't installed by default.

I have no idea what it is you think needs changing here.
Comment by Stéphane Gaudreault (stephane) - Thursday, 10 January 2013, 14:11 GMT
Isn't already the case? I do not have syslog-ng or rsyslog on my machine and journald work out of the box.
Comment by greg one (greg1) - Thursday, 10 January 2013, 14:12 GMT
Dave, ideally when you remove syslog-ng it should remove all traces of syslog from systemd files, please have a look here:
https://bbs.archlinux.org/viewtopic.php?id=146295

for now if you or system update replaced syslog-ng with journald you have syslog.service error right away, which isnt nice to see and is very confusing, there is more to it, systemd files in /usr/lib/systemd/system need to be cleaned from syslog entries and replaced by journald service wherever necessary - i wouldnt know how to handle this, whether it should be handled by removing syslog-ng or by installing systemd/journald package or by other means i dont know
Comment by Dave Reisner (falconindy) - Thursday, 10 January 2013, 14:18 GMT
No, I'm not going to be deleting symlinks that are user created on package removal.

You're responsible for your own system. You created that symlink, you can remove it, too.
Comment by جاك الفضة (jacksilver) - Thursday, 10 January 2013, 14:22 GMT
pacman -Q -o /usr/lib/systemd/system/syslog.socket show that this file is installed by systemd by default. I was think that mean that I need syslog on a new install, unless I got

syslog.service loaded inactive dead syslog.service
Comment by greg one (greg1) - Thursday, 10 January 2013, 14:24 GMT
as far as i remember i didnt create any symlink :)

Loading...