On Wed, 23.03.11 19:55, nerdopolis (bluescreen_aven...@verizon.net) wrote:
> > I think chroot can be a useful tool for jailing particular services into
> > subtrees of the fs hierarchy. Either in the way that the service itself
> > internally chroot()s (which Avahi does, as I think the only servic
On Monday, October 25, 2010 08:40:50 PM Lennart Poettering wrote:
> On Tue, 26.10.10 00:44, Michael Biebl (mbiebl at gmail.com) wrote:
> > 2010/10/26 Lennart Poettering :
> > > Note that we do not support booting a real system with systemd on PID
> > > != 1. The primary reason for that is that we n
On Fri, 05.11.10 17:11, Robert Schwebel (r.schwe...@pengutronix.de) wrote:
>
> On Tue, Oct 26, 2010 at 12:26:04AM +0200, Lennart Poettering wrote:
> > Sorry for the delayed reply. Needed to think a bit about this.
> >
> > Your patch would break running "systemd --system --test" to verify the
> >
On Tue, Oct 26, 2010 at 12:26:04AM +0200, Lennart Poettering wrote:
> Sorry for the delayed reply. Needed to think a bit about this.
>
> Your patch would break running "systemd --system --test" to verify the
> systemd setup as normal user, since that second instance would fight
> for the same socke
On Tue, 26.10.10 00:44, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2010/10/26 Lennart Poettering :
> > Note that we do not support booting a real system with systemd on PID !=
> > 1. The primary reason for that is that we need the SIGCHLD signals
> > properly, and we only get those as PID 1. Ear
2010/10/26 Lennart Poettering :
> Note that we do not support booting a real system with systemd on PID !=
> 1. The primary reason for that is that we need the SIGCHLD signals
> properly, and we only get those as PID 1. Early systemd versions
> supported a mode where we didn't rely on those signals
On Fri, 15.10.10 12:25, Robert Schwebel (r.schwe...@pengutronix.de) wrote:
> We currently only create the private D-Bus server when pid == 1, but
> this has also to be done if the user started us with --system.
> Otherwhise we get this error:
>
> systemd-cgroups-agent[164]: Failed to get D-Bus
On Fri, Oct 15, 2010 at 12:25:17PM +0200, Robert Schwebel wrote:
> We currently only create the private D-Bus server when pid == 1, but
> this has also to be done if the user started us with --system.
> Otherwhise we get this error:
>
> systemd-cgroups-agent[164]: Failed to get D-Bus connection:
We currently only create the private D-Bus server when pid == 1, but
this has also to be done if the user started us with --system.
Otherwhise we get this error:
systemd-cgroups-agent[164]: Failed to get D-Bus connection:
Failed to connect to socket /org/freedesktop/systemd1/private: Connectio
