On Mon, Jul 18, 2016 at 4:30 PM, Holger Kiehl wrote:
>
> I am beginning to wonder, even if I write proper unit files (using templates),
> the user is allowed to start and stop his AFD, either via command line or GUI.
> If he now does it with the provided tools, the process will again end up in
> t
Hi,
the systemd.unit man page is not quite clear on this, i.e. which
settings support which specifiers.
But maybe I just missed it.
I was wondering if I can use
ConditionPathExists=/dev/%i
Seems like this would e.g. be useful in [email protected], which currently has
ConditionPathExists=/dev/tty0
18.07.2016 17:35, Frank Steiner пишет:
> Hi,
>
> on some of our servers (all of those are NFS-servers with iscsi devices...)
> rebooting sometimes hangs after
>
> [ OK ] Reached target Shutdown.
>
> The next line, the kernel mesage about resetting the system, never
> shows up. Is there a way t
2016-07-18 15:34 GMT+02:00 Michael Biebl :
>
> I was told that this is already configurable in lxc via lxc.haltsignal.
> So afaics, lxc-create would just need to make sure to set this
> accordingly on distros which use systemd by default.
FYI: I've filed https://bugs.debian.org/cgi-bin/bugreport.c
On Mon, 18.07.16 15:17, Clemens Gruber ([email protected]) wrote:
> Hi,
>
> On Mon, Jul 18, 2016 at 03:02:10PM +0200, Lennart Poettering wrote:
> > Well, if they don't want to make SIGRTMIN+4 the default because they
> > think sysvinit/Upstart is more relevant than systemd, then that's
On Mon, 18 Jul 2016, Lennart Poettering wrote:
On Mon, 18.07.16 14:00, Michael Biebl ([email protected]) wrote:
2016-07-18 13:54 GMT+02:00 Lennart Poettering :
On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
Wh
On Fri, 15 Jul 2016, Mantas Mikulėnas wrote:
> On Thu, Jul 14, 2016 at 3:34 PM, Holger Kiehl wrote:
> Hello,
>
> I am new to systemd and the maintainer of the file distribution
> software
> AFD (http://www.dwd.de/AFD) and I am trying to adapt this
> application
>
On Fri, 15 Jul 2016, Andrei Borzenkov wrote:
> 15.07.2016 13:28, Holger Kiehl пишет:
> > I tried to avoid Type=forking and PIDFile= because I then have to maintain
> > two different init versions, systemd and System-V-Init. I think there will
> > always be other Unix systems around without systemd
2016-07-18 15:02 GMT+02:00 Lennart Poettering :
> On Mon, 18.07.16 14:41, Michael Biebl ([email protected]) wrote:
>
>> 2016-07-18 14:00 GMT+02:00 Michael Biebl :
>> > 2016-07-18 13:54 GMT+02:00 Lennart Poettering :
>> >> On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
>> >>
>> >>> A
Hi,
On Mon, Jul 18, 2016 at 03:02:10PM +0200, Lennart Poettering wrote:
> Well, if they don't want to make SIGRTMIN+4 the default because they
> think sysvinit/Upstart is more relevant than systemd, then that's
> their right. But I think making the kill signal configurable per
> container would pr
On Mon, 18.07.16 14:51, Michael Biebl ([email protected]) wrote:
> 2016-07-18 14:46 GMT+02:00 Lennart Poettering :
> > I'd really recommend them to switch to SIGRMIN+4 instead. Redefining
> > the meaning of SIGPWR like they are doing is certainly a bad idea.
> >
> > Note that this is even documente
On Mon, 18.07.16 14:41, Michael Biebl ([email protected]) wrote:
> 2016-07-18 14:00 GMT+02:00 Michael Biebl :
> > 2016-07-18 13:54 GMT+02:00 Lennart Poettering :
> >> On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
> >>
> >>> Apparently SIGPWR is used by lxc-stop to shut down LXC co
On Mon, 18.07.16 14:00, Michael Biebl ([email protected]) wrote:
> 2016-07-18 13:54 GMT+02:00 Lennart Poettering :
> > On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
> >
> >> Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
> >> What interface would you recommend
2016-07-18 14:46 GMT+02:00 Lennart Poettering :
> I'd really recommend them to switch to SIGRMIN+4 instead. Redefining
> the meaning of SIGPWR like they are doing is certainly a bad idea.
>
> Note that this is even documented here since a long time:
>
> https://www.freedesktop.org/wiki/Software/sys
2016-07-18 14:00 GMT+02:00 Michael Biebl :
> 2016-07-18 13:54 GMT+02:00 Lennart Poettering :
>> On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
>>
>>> Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
>>> What interface would you recommend instead?
>>>
>>> https://l
2016-07-18 13:54 GMT+02:00 Lennart Poettering :
> On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
>
>> Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
>> What interface would you recommend instead?
>>
>> https://lists.linuxcontainers.org/pipermail/lxc-users/2015-M
On Mon, 18.07.16 13:37, Michael Biebl ([email protected]) wrote:
> Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
> What interface would you recommend instead?
>
> https://lists.linuxcontainers.org/pipermail/lxc-users/2015-May/009279.html
Is that actually really used? I mean,
Apparently SIGPWR is used by lxc-stop to shut down LXC containers.
What interface would you recommend instead?
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-May/009279.html
2016-07-18 12:36 GMT+02:00 Lennart Poettering :
> On Sat, 16.07.16 17:22, Christian Hofstaedtler ([email protected])
On Sat, 16.07.16 17:22, Christian Hofstaedtler ([email protected]) wrote:
> Hi,
>
> I'm trying to understand how sigpwr.target is intended to be used,
> but couldn't find a good explanation. systemd.special says this
> target is invoked in a power fail situation, but what should happen
> then?
>
> De
19 matches
Mail list logo
