On Tue, 2010-09-07 at 02:41 +0200, Michał Piotrowski wrote: > Hi, > > I want to compare systemd and upstart boot speed (I don't expect much, > so I won't be disappointed :)) > > systemd > http://i56.tinypic.com/ilk4fq.jpg > > upstart > http://i53.tinypic.com/dnhrvm.png > > both starts system in 31 seconds, but systemd starts much more services. > > It looks like ntsysv doesn't have a systemd support. How can I disable > service in systemd? I suppose I need to use systemctl disable command, > but I don't know when to look for job names - list-jobs fails here > > [michal@dio ~]$ systemctl list-jobs > Failed to issue method call: Launch helper exited with unknown return code 1 > [michal@dio ~]$ sudo systemctl list-jobs > Failed to get D-Bus connection: Failed to connect to socket > /org/freedesktop/systemd1/private: Connection refused > [michal@dio ~]$ sudo systemctl list-units > Failed to get D-Bus connection: Failed to connect to socket > /org/freedesktop/systemd1/private: Connection refused > > Regards, > Michal That sounds like you have some kind of dbus bug on your system. To answer your main question, though, if the service is still a SysV service, you can still disable it just as you would have done before - 'chkconfig ntsysv off'. It's only systemd-native services that need the use of systemctl. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
