[Bug 1035062] New: Tumbleweed no longer executes scripts in /etc/init.d

newer
[Bug 1035062] Tumbleweed no longer...

older
[Bug 1035609] New: Bind doesn't...

bugzilla_noreply＠novell.com

20 Apr 2017 20 Apr '17

04:30

http://bugzilla.opensuse.org/show_bug.cgi?id=1035062 Bug ID: 1035062 Summary: Tumbleweed no longer executes scripts in /etc/init.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jeromed@tpg.com.au QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- As per the tital the latest updates of TW no longer execute scripts in /etc/init.d. The following are 2 examples of the problem I have encounted. 1 - I have a cut down TW server running named and openvpn. Noticed since the second last update neither the openvpn and named scripts now execute on init and I have to manually run them. 2 - To confirm point I also have a TW install on a laptop with KDE and virtual box no longer runs, complains of missing drivers. Upon investigating further vbox have 2 scripts in /etc/init.d that needs to execute on startup, manually running them fixes any issues with VirtualBox. Please let me know if you need any further information, i could not find any meaningful message in dmesg or journalctl. Cheers and thanks Jerome -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 2.9 KB)

Show replies by date

bugzilla_noreply＠novell.com

22 Apr 22 Apr

07:09

New subject: [Bug 1035062] Tumbleweed no longer executes scripts in /etc/init.d

http://bugzilla.opensuse.org/show_bug.cgi?id=1035062 http://bugzilla.opensuse.org/show_bug.cgi?id=1035062#c4 --- Comment #4 from JJ JJ --- Hi, the named files are located in /run/systemd/generator.late dir, as follows: drwxr-xr-x 2 root root 140 Apr 22 16:48 ./ drwxr-xr-x 18 root root 460 Apr 22 16:51 ../ -rw-r--r-- 1 root root 338 Apr 22 16:48 after.local.service -rw-r--r-- 1 root root 335 Apr 22 16:48 halt.local.service -rw-r--r-- 1 root root 407 Apr 22 16:48 local.service -rw-r--r-- 1 root root 558 Apr 22 16:48 named.service -rw-r--r-- 1 root root 609 Apr 22 16:48 openvpn.service systemctl enable named output is named.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable named Upon reboot named is not running, i have to issue command 'systemctl start named', and all is OK. I created my own openvpn script in init.d using insserv, again this was working before update 20170414 i think. Sorry if I am putting this in the wrong place, my first time using bugzilla. Thanks Jerome -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

07:10

New subject: [Bug 1035062] Tumbleweed no longer executes scripts in /etc/init.d

http://bugzilla.opensuse.org/show_bug.cgi?id=1035062 JJ JJ changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jeromed@tpg.com.a | |u) | -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Apr 24 Apr

10:24

New subject: [Bug 1035062] Tumbleweed no longer executes scripts in /etc/init.d

http://bugzilla.opensuse.org/show_bug.cgi?id=1035062 http://bugzilla.opensuse.org/show_bug.cgi?id=1035062#c7 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com --- Comment #7 from Franck Bui --- (In reply to Thorsten Kukuk from comment #6)

...

(In reply to Thomas Blume from comment #5)

...
We need to keep this symlink for backward compatibility. Thorsten, can you please take over?

Backward compatibility for software, which was written after LSB introduced the the LSB SysV init script standard???

Sorry, please fix systemd that it works on LSB SysV init systems and not only on RHEL.

Can you point out the refspec that specifies that symlinks should live in /etc/init.d ? And that's funny to see how you are very careful to prevent new changes that would break existing tools and in this case you simply ignore existing software that might rely on /etc/rc*.d ... BTW why did you make this change ? is this a pure cosmetic change or something else ? -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Apr 25 Apr