On Fri, Nov 18, 2016 at 6:52 PM arnaud gaboury
wrote:
> On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury
> wrote:
>
> On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
> wrote:
>
> A recent change (upgrade ?) in my setup broke the network in my container.
> Network is OK on the host, but not on the
On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury
wrote:
> On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
> wrote:
>
> A recent change (upgrade ?) in my setup broke the network in my container.
> Network is OK on the host, but not on the container.
>
> My setup:
>
> Host: Archlinux -
> % systemctl
On Fri, 18.11.16 15:46, Cédric BRINER ([email protected]) wrote:
> Hi,
>
> We used to have a custom init script written for systemV that was working.
>
> Now, for some unknown reason, systemd does not to treat this init script
> as it used to be.
>
> The init script is a bit odd, as it doe
Am 18.11.2016 um 15:46 schrieb Cédric BRINER:
We used to have a custom init script written for systemV that was working.
Now, for some unknown reason, systemd does not to treat this init script
as it used to be
If so how can I instruct this service to execute the ExecStop before
unmounting th
Hi,
We used to have a custom init script written for systemV that was working.
Now, for some unknown reason, systemd does not to treat this init script
as it used to be.
The init script is a bit odd, as it does not start the daemon itself.
This task is done by an admin that launches it through t
On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
wrote:
> A recent change (upgrade ?) in my setup broke the network in my container.
> Network is OK on the host, but not on the container.
>
> My setup:
>
> Host: Archlinux -
> % systemctl --version
> systemd 231
> +PAM -AUDIT -SELINUX -IMA -APPARMOR
A recent change (upgrade ?) in my setup broke the network in my container.
Network is OK on the host, but not on the container.
My setup:
Host: Archlinux -
% systemctl --version
systemd 231
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SE
On Fri, 18.11.16 10:26, Jakub Filak ([email protected]) wrote:
> Hello,
>
> I have a question regarding journald and backward compatibility. Are there
> any known issues with accessing journals that were created by different
> versions of journald?
>
> I want to use the latest libsystemd in my p
On Fri, 18.11.16 02:55, Masoom Shaikh ([email protected]) wrote:
> I have a container using debootstrap for Ubuntu 12.04
>
> systemd-nspawn -D ubuntu_12.04 works
>
>
> but I want it with boot option
>
> systemd-nspawn -bD ubuntu_12.04
>
> this doesn't give a console!
>
>
> read somewh
Hello,
I have a question regarding journald and backward compatibility. Are there
any known issues with accessing journals that were created by different
versions of journald?
I want to use the latest libsystemd in my project but I might end up reading
journals created by an ancient systemd (e.g.
10 matches
Mail list logo
