Hi, On Fri, Apr 11, 2014 at 02:03:52PM -0700, Linda Walsh wrote:
Richard Brown wrote:
On 9 April 2014 18:28, Roman Drahtmueller <draht@suse.de> wrote:
Having an init script and not needing it is better than needing it and not having it. Apparently, it doesn't harm, but rather helps.
I disagree - having both the systemd service file and the /etc/init.d file present on an installed machine causes confusion, both at a system level (eg. different answers to /etc/init.d/SuSEfirewall2 status and systemctl status SuSEfirewall) and at a sysadmin level ("What command do I use to do X?" - we don't want to have 2 different commands with 2 different results serving the same purpose)
Then get rid of the systemd interface -- it is confusing. No new commands for everyone to learn, no new "everything is different" problems -- I noted that even samba was recently called out for not being compatible with systemd's "quirks" and requirements -- of course the fact that it's been a working project for 15+ years is inconsequential. All must adapted to the new dominator.... *blech*.
About which issue are you talking? That systemd is a bit fast with starting the daemons and therefore we get in the syslog lines like like the following: PID file /run/samba/winbindd.pid not readable (yet?) See https://bugs.freedesktop.org/show_bug.cgi?id=66641 and https://bugzilla.redhat.com/show_bug.cgi?id=911819 Systemd only is a bit fast. If that's what you have in mind go and file a bugreport and I'm quite sure it will get closed with the reason: it's a feature and not a bug. There are much more broken and important things to work on. But feel free to offer real arguments in bugzilla. You're aware that the service <service-name> <command> syntax is still the same as before? And even tab completion works for the service name. The rc<service_name> sym links also work. All you no longer have is /etc/init.d/<service-name> If it's something different we need a bug report. Please be this nice and report the BUG ID back to this thread and also add to the bug report a link to the thread at http://lists.opensuse.org/opensuse-factory What we don't need are long endless, useless, and fruitless discussions. In particular now several releases after we made the switch to systemd as the only init system. And the real hard work now _is_ done.
I agree with the argument that having the sysVinit script is good for non-systemd build targets, but for openSUSE 13.2 and beyond we use systemd, and in our distro, we should only be using systemd unit files
Why? Because you will feel uncomfortable and insecure if anyone is still running sysVinit on their 13.2 system?
To keep it simple and stupid. To focus on one system to start services. To nail as many issue as possible. And we made the migration quite smooth. With openSUSE we had two systems available for quite some time. Check the Debian side and their discussion regarding systemd and see the comments from the upstart inventor after they decided to go with systemd too. See also the hard work and count the many hours spent on systemd to get it to the current level of quality as we have with openSUSE. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany