https://bugzilla.novell.com/show_bug.cgi?id=839032 https://bugzilla.novell.com/show_bug.cgi?id=839032#c Ye Yuan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@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=839032 https://bugzilla.novell.com/show_bug.cgi?id=839032#c2 Volker Kuhlmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #2 from Volker Kuhlmann 2013-10-18 00:50:55 NZDT --- In syslog, which is archived in /var/log/messages. It happens early while booting too, when systemd starts up: [ 21.686644] systemd[1]: systemd 195 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; suse) [ 21.881235] systemd[1]: Inserted module 'autofs4' [ 22.211129] systemd[1]: [/etc/systemd/system/faxgetty.service:16] Failed to add dependency on ypbind, ignoring: Invalid argument [ 22.211147] systemd[1]: [/etc/systemd/system/faxgetty.service:17] Failed to add dependency on isdn, ignoring: Invalid argument [ 22.413915] systemd[1]: Cannot add dependency job for unit cyrus.service, ignoring: Unit cyrus.service failed to load: No such file or directory. See system logs and 'systemctl status cyrus.service' for details. [ 22.413921] systemd[1]: Cannot add dependency job for unit ldap.service, ignoring: Unit ldap.service failed to load: No such file or directory. See system logs and 'systemctl status ldap.service' for details. [ 22.418888] systemd[1]: Starting Replay Read-Ahead Data... The errors seem to be generated whenever service dependency is recalculated or requested, e.g. when running chkconfig. Contrary to popular statements, chkconfig is not superseeded by systemd, it is actively required by the large number of services still without systemd files. ddclient is just my latest example. -- 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=839032 https://bugzilla.novell.com/show_bug.cgi?id=839032#c Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- 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=839032 https://bugzilla.novell.com/show_bug.cgi?id=839032#c6 --- Comment #6 from Volker Kuhlmann 2013-11-28 08:08:43 NZDT --- There are a large number of service packages around that have no systemd support. Whoever thinks adding systemd support for hylafax will fix openSUSE is deluding themselves. I am using hylafax with the openSUSE supplied /etc/init.d/hylafax. For faxgetty I was forced to hack up my own systemd file because I need hylafax to work, and it seems I forgot to publish it. It's now here: http://volker.top.geek.nz/linux/system/ Having a systemd-only openSUSE is wishful thinking. It's been years in coming (suboptimal management from the user's POV) and will take years more. To be honest I lost interest because of the requirement for a computer science degree to use it. It's phenomenally complex for little extra gain over sysv init and a huge amount of time wasted on all the conversions. If it was more useable, ... but it's not. Perhaps my faxgetty systemd file is buggy - that's what I came up with and I haven't filed an oS bug for that. Does this warrant the ldap and cyrus errors though? I don't see any relationship between faxgetty and two services that aren't even installed! -- 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=839032 https://bugzilla.novell.com/show_bug.cgi?id=839032#c8 --- Comment #8 from Volker Kuhlmann 2013-11-29 12:36:38 NZDT --- Would be more than happy to test, have been wondering about hylafax+ anyway, but am hopelessly behind my projects. Is this hylafax+? http://download.opensuse.org/repositories/home:/DocB/openSUSE_12.3/x86_64/hy... The name doesn't indicate it, and it is a different branch, both are maintained as far as I am aware. I can only test on 12.3 and simply do not have the time to deal with an upgrade to 13.1. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=839032 --- Comment #9 from David Rankin --- (In reply to Volker Kuhlmann from comment #8)

Would be more than happy to test, have been wondering about hylafax+ anyway, but am hopelessly behind my projects.

Is this hylafax+? http://download.opensuse.org/repositories/home:/DocB/openSUSE_12.3/x86_64/ hylafax-5.5.2-7.3.x86_64.rpm

The name doesn't indicate it, and it is a different branch, both are maintained as far as I am aware. I can only test on 12.3 and simply do not have the time to deal with an upgrade to 13.1.

No it's not hylafax+ it is rather a older version of hylafax for 12.3. I suspect, but have not confirmed, that the problem you are seeing with the noise is due to an old cyrus dependency from the older SysV init setup that has been migrated into a service file or target somewhere. The cyrus dependency was common to a large number of files and has been hanging around in some form or another for at least the past 10 releases (8.0-pro days?) Many of the old mail auth routines made use of cyrus.imap features regardless of whether cyrus was selected for install or not. Rather than chase this dependency down the 12.3 rabbit-hole, it probably makes sense to see whether this noise continues in factory. As a large number of the systemd targets and services files have revised/improved since 12.3 release. While hylafax makes use of faxgetty, faxgetty isn't limited to hylafax. It is the general tty for fax services, if I recall correctly, configured (enabled/disable) in the old inittab, as needed. In addition to hylafax, I believe some desktops make use of it in generic fax handling print interfaces. Needless to say, the dependency that is triggering the log output could come for one of dozen packages. I'll see if I can get others in to take a loop as I don't have a 12.3 install to test (and am somewhat bewildered how this bug was assigned to me, other than it mentions hylafax...) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=839032 --- Comment #10 from Volker Kuhlmann --- Thanks David! The warnings/errors still show up in systemd's log when the system boots. However I expect 12.3 will be out of support soon and I expect to upgrade to 13.2 by the end of the year. It's probably better to put the effort into 13.2 and I'll investigate the problem then. If the change to hylafax+ has happened by 13.2 I'll need to look into things anyway. -- You are receiving this mail because: You are on the CC list for the bug.