On Sat, Oct 27, 2012 at 11:59:21AM -0400, Michael H. Warfield wrote: > On Sat, 2012-10-27 at 10:05 +0200, Miklos Vajna wrote: > > On Fri, Oct 26, 2012 at 06:39:33PM -0400, "Michael H. Warfield" > > <m...@wittsend.com> wrote: > > > [root@alcove mhw]# systemctl status network.service > > > network.service - LSB: Bring up/down networking > > > Loaded: loaded (/etc/rc.d/init.d/network) > > > Active: failed (Result: exit-code) since Wed, 24 Oct 2012 > > > 18:23:07 +0400; 1min 57s ago > > > Process: 91 ExecStart=/etc/rc.d/init.d/network start (code=exited, > > > status=209/STDOUT) > > > CGroup: name=systemd:/system/lxc/Alcove/system/network.service > > > > > > Tells me nothing. Does not tell me where the problem is... > > > > What systemd version are you running? Seems some older one, which lacks > > journal integration, providing the stderr/stdout of the failed service. > > > I guess that would help a lot in your situation. > > I think you're onto something there. I'm running the latest for Fedora > 17 but that's only systemd-44-20. Building that reveals a whole lot of > "cherry picked" patches from git commits. Rawhide has systemd-194-1 and > I've now built that for F17 and appears to be a cleaner build. I'm > going to test with that one first before moving on to git.
Fedora 18 have probably more recent version than rawhide. At last receiving more attention. -- Tomasz Torcz To co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
