[Bug 843659] New: systemd: syslog.service vs. syslog-ng-service ?
https://bugzilla.novell.com/show_bug.cgi?id=843659 https://bugzilla.novell.com/show_bug.cgi?id=843659#c0 Summary: systemd: syslog.service vs. syslog-ng-service ? Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: per@computer.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I installed syslog-ng, and then started it with "systemctl start syslog", no problems. Then I tried to enable it: linux:~ # systemctl enable syslog Failed to issue method call: No such file or directory linux:~ # systemctl enable syslog.service Failed to issue method call: No such file or directory linux:~ # systemctl status syslog syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Wed 2013-10-02 11:08:12 CEST; 2min 16s ago Process: 6518 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS) Main PID: 6522 (syslog-ng) CGroup: /system.slice/syslog-ng.service └─6522 /usr/sbin/syslog-ng -F Oct 02 11:08:12 taggart7 systemd[1]: Starting System Logging Service... Oct 02 11:08:12 taggart7 systemd[1]: Started System Logging Service. linux:~ # systemctl enable syslog-ng.service Why? It doesn't seem very intuitive to have two names ? Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=843659 https://bugzilla.novell.com/show_bug.cgi?id=843659#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=843659 https://bugzilla.novell.com/show_bug.cgi?id=843659#c1 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com, | |pczanik@genesi-usa.com, | |werner@suse.com AssignedTo|werner@suse.com |mt@suse.com --- Comment #1 from Dr. Werner Fink <werner@suse.com> 2013-11-04 10:17:12 UTC --- syslogd.service != syslog.target != syslog-ng.service ... beside this all three services syslog-ng.service, syslogd.service,rsyslog.servic and uses an alias syslog.service IMHO this bug report is invalid -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=843659 https://bugzilla.novell.com/show_bug.cgi?id=843659#c2 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #2 from Marius Tomaschewski <mt@suse.com> 2013-11-04 10:32:12 UTC --- (In reply to comment #0)
linux:~ # systemctl enable syslog
You have to use "systemctl enable/disable syslog-ng" == using the name of the implementation of the system syslog service you want to use. The enablement will create a link syslog-ng.service -> syslog.service, which allows to use "systemctl start/stop/reload syslog", that is the current system syslog service, e.g. in log rotation config files, ...
Why? It doesn't seem very intuitive to have two names ?
No, this is how it works with systemd [and foo vs. $foo in systemv world]. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com