[systemd-devel] One of my fundamental problems with systemd...

[Miklos Vajna]

On Sat, Oct 27, 2012 at 08:20:51AM -0400, "Michael H. Warfield" <mhw at WittsEnd.com> wrote:
> On Sat, 2012-10-27 at 10:03 +0200, Miklos Vajna wrote:
> > On Fri, Oct 26, 2012 at 06:39:33PM -0400, "Michael H. Warfield" <mhw at WittsEnd.com> wrote:
> > > [root at 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'm running the latest one on Fedora 17...
> 
> [mhw at forest ~]$ rpm -qa | grep systemd
> systemd-44-20.fc17.x86_64
> systemd-sysv-44-20.fc17.x86_64

Odd, the oldest systemd version I have around is 38, and even that has a
working journal that catches stdout/stderr of services.