On Mon, 2012-10-22 at 02:53 +0200, Kay Sievers wrote:
> On Sun, Oct 21, 2012 at 11:25 PM, Michael H. Warfield
> wrote:
> > This is being directed to the systemd-devel community but I'm cc'ing the
> > lxc-users community and the Fedora community on this for their input as
> > well. I know it's no
On Sun, Oct 21, 2012 at 11:25 PM, Michael H. Warfield wrote:
> This is being directed to the systemd-devel community but I'm cc'ing the
> lxc-users community and the Fedora community on this for their input as
> well. I know it's not always good to cross post between multiple lists
> but this is
On Thu, 18.10.12 14:42, Lukáš Nykrýn ([email protected]) wrote:
>
> Kay Sievers píše v St 17. 10. 2012 v 18:28 +0200:
> > On Wed, Oct 17, 2012 at 6:10 PM, Lennart Poettering
> > wrote:
> > > On Wed, 17.10.12 14:16, Lukáš Nykrýn ([email protected]) wrote:
> > >
> > >> Hello,
> > >> Today I have
Hello,
This is being directed to the systemd-devel community but I'm cc'ing the
lxc-users community and the Fedora community on this for their input as
well. I know it's not always good to cross post between multiple lists
but this is of interest to all three communities who may have valuable
inp
Le dimanche 21 octobre 2012 à 15:59 +0400, Andrey Borzenkov a écrit :
> This issue comes up relatively often on openSUSE forums. Users
> complaint that when system drops in emergency, there is nothing that
> would explain user why it happened or what to do. Typical situation is
> https://bugzilla.n
On Sun, Oct 21, 2012 at 12:27:55PM +0100, Valere Monseur wrote:
> Hi,
>
> In a recent commit: "units: rework systemd-exit.service to terminate systemd
> via signal rather..." changes have been made in configure.ac
> There might be a bug in this line:
>
> AC_PATH_PROG([KILL], [kill], [/usr/bin/cap
This issue comes up relatively often on openSUSE forums. Users
complaint that when system drops in emergency, there is nothing that
would explain user why it happened or what to do. Typical situation is
https://bugzilla.novell.com/show_bug.cgi?id=782904.
openSUSE by default is using "splash quiet"
Hi,
In a recent commit: "units: rework systemd-exit.service to terminate systemd
via signal rather..." changes have been made in configure.ac
There might be a bug in this line:
AC_PATH_PROG([KILL], [kill], [/usr/bin/cap])
Is the /usr/bin/cap normal ?
or is it a typo and so should be /usr/bin/
