On Mon, 30.05.16 10:51, Simon McVittie ([email protected]) wrote:
> On 29/05/16 19:39, Barry Scott wrote:
> > I just came across the bootctl command. Atleast on Fedora 23 and 24
> > it errors out because /boot is not FAT EFI. I thought that if you are EFI
> > then the EFI was always i
On Sun, 29.05.16 19:39, Barry Scott ([email protected]) wrote:
> I just came across the bootctl command. Atleast on Fedora 23 and 24
> it errors out because /boot is not FAT EFI. I thought that if you are EFI
> then the EFI was always in /boot/efi.
/boot and the ESP exist for the same reason
On 05/30/2016 06:04 PM, Lennart Poettering wrote:
On Mon, 30.05.16 16:24, george Karakou ([email protected]) wrote:
Hi again, i am a bit curious about these two directives. Can somebody
explain in a few words how are these implemented? Using linux network
namespaces? Or simply put s
On Sun, 29.05.16 13:28, Felix Miata ([email protected]) wrote:
> Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200):
>
> >Felix Miata wrote:
>
> >>The message I see is equivalent in form as during boot, e.g. when a
> >>filesystem not noauto in fstab is to be mounted but cannot be fou
On Mon, 30.05.16 16:24, george Karakou ([email protected]) wrote:
> Hi again, i am a bit curious about these two directives. Can somebody
> explain in a few words how are these implemented? Using linux network
> namespaces? Or simply put somehow services using these 2 directives are
> fo
On 05/30/2016 04:32 PM, Mantas Mikulėnas wrote:
On Mon, May 30, 2016 at 4:24 PM, george Karakou
mailto:[email protected]>> wrote:
Hi again, i am a bit curious about these two directives. Can
somebody explain in a few words how are these implemented? Using
linux network n
On Mon, May 30, 2016 at 4:24 PM, george Karakou
wrote:
> Hi again, i am a bit curious about these two directives. Can somebody
> explain in a few words how are these implemented? Using linux network
> namespaces? Or simply put somehow services using these 2 directives are
> forbidden to bind to
Hi again, i am a bit curious about these two directives. Can somebody
explain in a few words how are these implemented? Using linux network
namespaces? Or simply put somehow services using these 2 directives are
forbidden to bind to l3, l4 sockets and only allowed to communicate via
unix domai
Okay, thank you: now I see the purpose of systemd's jobs.
So, if I get it well: if I want to monitor any kind of service
(Type=oneshot, Type=simple, etc.), I need to catch UnitRemoved event and
invoke the LoadUnit to get the status of the stopped (either in failure or
in success) Unit, right?
The
Any Start/Stop/Restart operation you issue creates a job that will
eventually (almost immediately, when starting a Type=simple service) get
completed (or fail) and trigger a JobRemoved signal containing the result.
When StartUnit/StopUnit/etc return they give you the job's object path you
need to
Thank you! I'll try that ASAP. Do I need to listen to JobRemoved because I
use the [type=oneshot] or is it the way to do for every kind of service
(like [type=simple], for example)?
I'm asking that because I just dicovered that [systemctl list-jobs] lists
my [type=oneshot] service when I start it,
On Sun, 29.05.16 22:24, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> On Sun, May 29, 2016 at 10:59:23AM +0200, Peter Lemenkov wrote:
> > Hello All!
> > I'd like to introduce another systemd-related project -
> > erlang-sd_notify. That's just a bindings for sd_notify API. Currently
> >
On Sun, 29.05.16 20:45, Christian Lockley ([email protected]) wrote:
> Hi,
> Just wondering if it should be possible to add events the empty event loop.
222 is already pretty old. That said, adding events before running the
event loop is what we do pretty much everywhere, so this really *does*
On Sun, 29.05.16 20:41, Christian Lockley ([email protected]) wrote:
> Hi all,
> I developing an app that returns an id after and init function, this id is
> to be passed the subsequent calls so the program can prevent clients from
> modifying the internal state of other clients. Right now I st
On 29/05/16 19:39, Barry Scott wrote:
> I just came across the bootctl command. Atleast on Fedora 23 and 24
> it errors out because /boot is not FAT EFI. I thought that if you are EFI
> then the EFI was always in /boot/efi.
I think mounting the EFI System Partition on /boot/efi is likely to be
ver
On Mon, May 30, 2016 at 3:41 AM, Christian Lockley
wrote:
> Hi all,
> I developing an app that returns an id after and init function, this id
> is to be passed the subsequent calls so the program can prevent clients
> from modifying the internal state of other clients. Right now I store the
> va
Am 27.05.2016 um 09:40 schrieb Reindl Harald:
Am 27.05.2016 um 06:48 schrieb Thomas Güttler:
OK, I understand that I need different tool to restart a service
if a check-script fails.
In my case the check script will be custom code. But the restart stuff
is very general and reusable:
Step1
17 matches
Mail list logo
