On Tue, 2011-02-08 at 11:04 +0100, Lennart Poettering wrote:
On Tue, 08.02.11 04:44, Braden McDaniel (braden(a)endoframe.com)
> > > > what does "systemctl status NetworkManager.service" say?
> > >
> > > After booting and logging in as root:
> > >
> > > # systemctl status NetworkManager.service
> > > NetworkManager.service - Network Manager
> > > Loaded: loaded
> > > Active: inactive (dead)
> > > CGroup: name=systemd:/system/NetworkManager.service
> > >
> > Hmm, is it even enabled? Try "systemctl is-enabled NetworkManager.service
; echo $?" ?
> # systemctl is-enabled NetworkManager.service ; echo $?
So, it isn't enabled. A zero exit code means it is enabled, a non-zero
exit code means it isn't. (that's normal unix logic, even if it appears
Try enabling it via "systemctl enable NetworkManager.service"
Not sure what went wrong here, but normally this fragment in
Networkmanager.spec should ensure that the systemd service gets enabled
on upgrades from sysv versions:
%triggerin -- NetworkManager < 1:0.8.1-5
if /sbin/chkconfig NetworkManager ; then
/bin/systemctl enable NetworkManager.service >/dev/null 2>&1 || :
or is this a fresh install? if so, I am not entirely sure whose job it
is to enable NM initially after install. Dan?
I installed F14 from DVD and immediately did a yum upgrade to rawhide.
> I'm not sure whether "1" means it is or it
> system-config-services claims it's enabled.
s-c-s only covers sysv services. We probably should deprecate it or at
least add a bit of code to point out that whether a service is on or off
in sysv is ignored for native systemd services.
Why not fix it? That is, why should a user of this app care whether a
service is SysV or systemd? Or, is this app being replaced by some
Braden McDaniel <braden(a)endoframe.com>