This seems to putthe requirement of an If(a||b||c)==Failure Then
reboot.target
Where a b and c are ALL required to complete before rebooting occurs.
I would thing to specifically handle each tool as a process,
Would a specific script or tool already be available?
Is it possible to one-shot
Yes, I was referring to a container when using the name vm. Sorry if
I caused confusion with this, I used to run lots of real VMs and then
moved those over to containers and still think of those services as
virtual machines.
On Mon, Apr 27, 2015 at 5:01 PM, Lennart Poettering
Hello!
The man page reads:
[MATCH] SECTION OPTIONS
The network file contains a [Match] section, which determines if a
given network file may be applied to a given device; and a
[Network] section specifying how the device should be configured.
The first (in lexical
On Mon, 27.04.15 11:47, aaron_wri...@selinc.com (aaron_wri...@selinc.com) wrote:
I applied commit 628c89cc68ab96fce2de7ebba5933725d147aecc - core: rework
device state logic, but now I'm left with a random chance to boot or not.
Some boots it comes up with /var mounted and lots of nice
On Mon, 27.04.15 21:19, Ivan Shapovalov (intelfx...@gmail.com) wrote:
This is yet another attempt to fix coldplugging order (more especially,
the problem which happens when one creates a job during coldplugging and
it references a not-yet-coldplugged unit).
Now we forcibly coldplug all
On Mon, 27.04.15 20:11, Peter Paule (systemd-de...@fedux.org) wrote:
I'm guessing from the error message that it's not a shell script but nginx
itself configured to use /dev/stderr as its log file, so there's no
that could be used...
Correct - see
On Mon, 27.04.15 20:08, Kai Krakow (hurikha...@gmail.com) wrote:
Or in other words: ipv6 setup needs some manual networking setup on
the host.
Or there... Any pointers?
Not really. You have to set up ipv6 masquerading with ip6tables. And
ensure the containers get ipv6 addresses that are
On Mon, 27.04.15 20:17, Kai Krakow (hurikha...@gmail.com) wrote:
Tomasz Torcz to...@pipebreaker.pl schrieb:
Well, would that enable automatic, correcting routing between the
container and the host's external network? That's kinda what this all
is about...
If you have radvd running,
Lennart Poettering lenn...@poettering.net schrieb:
On Mon, 27.04.15 20:17, Kai Krakow (hurikha...@gmail.com) wrote:
Tomasz Torcz to...@pipebreaker.pl schrieb:
Well, would that enable automatic, correcting routing between the
container and the host's external network? That's kinda what
To install a Fedora container from the raw image in my host Archlinux,
I can do this:
# systemd-nspawn -M Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw --
bind=/var/lib/machines/enl:/mnt
Now for the use of two btrfs subvol, I would like to bind
/var/lib/machines/enl/{etc,var}
Does the systemd
At the moment the only user of system-update.target is PackageKit,
which does package updates offline in the special system-update boot
target. The other project that has just started using this mode is
fwupd, which is using it to update BIOS-based firmware (not UEFI
capsules) offline.
I've
On Fri, 24.04.15 12:37, Jonathan Boulle (jonathanbou...@gmail.com) wrote:
Naive question, perhaps, but why does systemd even need to umount when
being run in a mount namespace? Can't we let the kernel tear them down when
it exits?
Well, so far our intention there was to ensure that the
On Sun, 26.04.15 15:34, Peter Paule (systemd-de...@fedux.org) wrote:
Maybe syslog will do the trick?
Well, the journal will do the trick, if you run systemd inside your
container. If you don't, then bind mounting the syslog socket might
suffice.
BTW:
Do I need a syslog daemon to receive
On Sun, 26.04.15 14:32, Peter Paule (systemd-de...@fedux.org) wrote:
BTW: I did the `echo asdf /dev/stderr`-thing just to test if
`/dev/stderr` worked as expected.
/dev/stderr does not work for socket fds, and that's a kernel
limitation, systemd can't do much bout it.
What I do not
On Mon, 27.04.15 10:19, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
To install a Fedora container from the raw image in my host Archlinux,
I can do this:
# systemd-nspawn -M Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw --
bind=/var/lib/machines/enl:/mnt
Now for the use of two btrfs
On Mon, 27.04.15 16:59, Mantas Mikulėnas (graw...@gmail.com) wrote:
I'm guessing from the error message that it's not a shell script but nginx
itself configured to use /dev/stderr as its log file, so there's no
that could be used...
If this indeed is the case, try using /dev/console instead,
On Sat, 25.04.15 11:05, Nanda Kumar (nandakumar@gmail.com) wrote:
Hi,
I am facing problem while querying DNS using getaddrinfo() API under a
process initiated by systemd. Despite having nameserver entry in
/etc/resolv.conf, the query fails to resolve. After few system call traces,
it
On Sun, 26.04.15 21:04, Thomas H.P. Andersen (pho...@gmail.com) wrote:
On Sun, Apr 26, 2015 at 8:31 PM, Thomas H.P. Andersen pho...@gmail.com
wrote:
On Sun, Apr 26, 2015 at 8:23 PM, Shawn Landden sh...@churchofgit.com
wrote:
Actually you missed that free_sysvstub_hashmap does not
On Sun, 26.04.15 16:50, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've successfully created a Gentoo container on top of a Gentoo host. I can
start the container with machinectl. I can also login using SSH. So mission
almost accomblished (it should become a template for easy vserver
On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 27.04.15 10:19, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
To install a Fedora container from the raw image in my host Archlinux,
I can do this:
# systemd-nspawn -M
On Mon, 27.04.15 09:52, Richard Hughes (hughsi...@gmail.com) wrote:
At the moment the only user of system-update.target is PackageKit,
which does package updates offline in the special system-update boot
target. The other project that has just started using this mode is
fwupd, which is using
On 27 April 2015 at 15:01, Lennart Poettering lenn...@poettering.net wrote:
On Sun, 26.04.15 16:50, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've successfully created a Gentoo container on top of a Gentoo host. I can
start the container with machinectl. I can also login using SSH. So
On Sun, 26.04.15 16:55, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've successfully created a Gentoo container on top of a Gentoo host. I can
start the container with machinectl, as I can with systemctl start
Inside the container (logged in via SSH), I could issue a reboot
On Fri, 24.04.15 21:39, Andrei Borzenkov (arvidj...@gmail.com) wrote:
В Fri, 24 Apr 2015 20:19:33 +0200
Lennart Poettering lenn...@poettering.net пишет:
On Fri, 24.04.15 20:46, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On 2015-04-24 at 19:13 +0200, Lennart Poettering wrote:
On
On Sat, 25.04.15 00:14, Tobias Hunger (tobias.hun...@gmail.com) wrote:
Hello,
sorry (again) for the delay. I unfortunately can not check into this
as often as I would like:-(
Lennart: Thank you for that patch, that does indeed fix my issue with
read-only machine images.
The networking
On Sat, 25.04.15 01:44, Tobias Hunger (tobias.hun...@gmail.com) wrote:
By the way: Is there a way to get the journal from a --ephemeral container?
I had expected --link-journal=host to work, but --link-journal seems
to not be allowed in any way.
I figure we should teach journalctl -m to
On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 27.04.15 10:19, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
To install a Fedora container from the raw image in my host Archlinux,
I can do this:
# systemd-nspawn -M
On Sat, 25.04.15 21:07, Peter Paule (systemd-de...@fedux.org) wrote:
Hi Lennart,
I prepared a virtual machine to investigate the nginx-issue. This
virtual machine is very very basic and had no mkfs.btrfs installed and
no native btrfs-fs available.
When I tried to download a new dkr-image
On Apr 27, 2015 16:39, Lennart Poettering lenn...@poettering.net wrote:
On Sun, 26.04.15 14:32, Peter Paule (systemd-de...@fedux.org) wrote:
BTW: I did the `echo asdf /dev/stderr`-thing just to test if
`/dev/stderr` worked as expected.
/dev/stderr does not work for socket fds, and that's
On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote:
Well, networkd on the host automatically sets up IPv4 masquerading for
each container. We simply don't do anything equivalent for IPv6
currently.
Ideally we wouldn't have to do NAT for IPv6 to make this
On Mon, Apr 27, 2015 at 04:56:18PM +0200, Lennart Poettering wrote:
On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.led...@intel.com)
wrote:
Well, networkd on the host automatically sets up IPv4 masquerading for
each container. We simply don't do anything equivalent for IPv6
On 27 April 2015 at 15:18, Lennart Poettering lenn...@poettering.net wrote:
Well, thinking about this, maybe OnFailure=reboot.target is missing
the point for these services. After all, the system should reboot
regardless if the update fails or not...
Not quite; PackageKit supports an
On 27 April 2015 at 15:56, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.led...@intel.com)
wrote:
Well, networkd on the host automatically sets up IPv4 masquerading for
each container. We simply don't do anything equivalent for IPv6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I have discovered how to add resource limits for the user, like how
much memory the user can use, or how much cpu time.
Here is the problem: /tmp seems a way for the user to circumvent this
restriction. Is there a way to protect it too?
Lennart Poettering lenn...@poettering.net schrieb:
On Mon, 27.04.15 20:08, Kai Krakow (hurikha...@gmail.com) wrote:
Or in other words: ipv6 setup needs some manual networking setup on
the host.
Or there... Any pointers?
Not really. You have to set up ipv6 masquerading with ip6tables.
Hmm, but that already lists a native config keyword for stderr?
Yes, I saw that too late. I copied the default configuration of the Arch Linux
nginx package and used that.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On 2015-04-27 at 17:14 +0200, Lennart Poettering wrote:
On Sat, 25.04.15 05:48, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On 2015-04-25 at 04:00 +0300, Ivan Shapovalov wrote:
On 2015-04-24 at 16:04 +0200, Lennart Poettering wrote:
[...]
Actually, it really is about the
On 27 April 2015 at 16:42, Lennart Poettering lenn...@poettering.net wrote:
- ship a service packagekit-reboot.service that contains:
[Service]
ExecStart=/bin/systemctl reboot --no-block
Type=oneshot
If that file was shipped in systemd, fwupd could use the same method
without having to
On Sat, 25.04.15 15:51, Jan Janssen (medhe...@web.de) wrote:
Yeah, patches like these always do end up looking messy. It's much
easier to read after applying it.
Well, it jumps from one boot to the next boot using _BOOT_ID matches. It
starts at the journal head to get the boot ID, makes a
On Sat, 25.04.15 05:48, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On 2015-04-25 at 04:00 +0300, Ivan Shapovalov wrote:
On 2015-04-24 at 16:04 +0200, Lennart Poettering wrote:
[...]
Actually, it really is about the UNIT_TRIGGERS dependencies only,
since we don't do the
On Wed, 04.02.15 23:48, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
Sorry for the late reply,
On Wed, 2015-02-04 at 21:57 +0100, Lennart Poettering wrote:
OK, let's try this again, with an example:
a) you have one service mydaemon.service
b) you have a preparation service called
On Fri, 24.04.15 20:54, Mikhail Morfikov (mmorfi...@gmail.com) wrote:
On Fri, 24 Apr 2015 19:04:53 +0200
Lennart Poettering lenn...@poettering.net wrote:
On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote:
Sorry for the really late reply, still trying to work through
On Mon, 27.04.15 18:28, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On 2015-04-27 at 17:14 +0200, Lennart Poettering wrote:
On Sat, 25.04.15 05:48, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On 2015-04-25 at 04:00 +0300, Ivan Shapovalov wrote:
On 2015-04-24 at 16:04 +0200,
On Mon, 27.04.15 15:47, Richard Hughes (hughsi...@gmail.com) wrote:
On 27 April 2015 at 15:18, Lennart Poettering lenn...@poettering.net wrote:
Well, thinking about this, maybe OnFailure=reboot.target is missing
the point for these services. After all, the system should reboot
regardless
Martin Pitt martin.p...@ubuntu.com on Sat, 2015/04/11 10:38:
Hello Tobias,
Tobias Hunger [2015-04-11 2:17 +0200]:
did you make any progress with this bug? Apparently the same issue is
blocking systemd-219 from getting into arch linux (
https://bugs.archlinux.org/task/44016 ), so this
On 27 April 2015 at 17:53, Mantas Mikulėnas graw...@gmail.com wrote:
In this case, failure doesn't make much sense, if you describe the task as
ensuring that the BIOS is up-to-date.
In this case, the task is upload firmware blob foo.bin in /var/cache
to the flash chip
Richard.
This is the log when my system works as usual:
(loginctl session-status)
1 - morfik (1000)
Since: Sun 2015-04-26 23:19:01 CEST; 18h ago
Leader: 1720 (lightdm)
Seat: seat0; vc7
Display: :0
Service: lightdm; type x11; class user
State:
On Mon, Apr 27, 2015 at 11:52 AM, Richard Hughes hughsi...@gmail.com
wrote:
What return code I supposed to return if we launch
fwupd-offline-update.service and there are no BIOS updates to apply?
In this case, failure doesn't make much sense, if you describe the task as
ensuring that the BIOS
Lennart Poettering lenn...@poettering.net schrieb:
On Sun, 26.04.15 16:55, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've successfully created a Gentoo container on top of a Gentoo host. I
can start the container with machinectl, as I can with systemctl start
Inside the
Tomasz Torcz to...@pipebreaker.pl schrieb:
Well, would that enable automatic, correcting routing between the
container and the host's external network? That's kinda what this all
is about...
If you have radvd running, it should. By the way, speaking of NAT
in context of IPv6 is a heresy.
Lennart Poettering lenn...@poettering.net schrieb:
On Sun, 26.04.15 16:50, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've successfully created a Gentoo container on top of a Gentoo host. I
can start the container with machinectl. I can also login using SSH. So
mission almost
This is yet another attempt to fix coldplugging order (more especially,
the problem which happens when one creates a job during coldplugging and
it references a not-yet-coldplugged unit).
Now we forcibly coldplug all units which participate in jobs. This
is a superset of previously implemented
Lennart Poettering lenn...@poettering.net schrieb:
On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.led...@intel.com)
wrote:
Well, networkd on the host automatically sets up IPv4 masquerading for
each container. We simply don't do anything equivalent for IPv6
currently.
Kai Krakow hurikha...@gmail.com schrieb:
Amended below...
Hello!
I've created a container with systemd-nspawn, machinectl enabled it,
then added machines.target to my default target (systemctl enable
machines.target) so that containers will be autostarted on boot. That
works so far.
I'm guessing from the error message that it's not a shell script but nginx
itself configured to use /dev/stderr as its log file, so there's no
that could be used...
Correct - see http://nginx.org/en/docs/ngx_core_module.html
Syntax: error_log file | stderr |
On Mon, Apr 27, 2015 at 9:11 PM, Peter Paule systemd-de...@fedux.org
wrote:
I'm guessing from the error message that it's not a shell script but
nginx
itself configured to use /dev/stderr as its log file, so there's no
that could be used...
Correct - see
I feel like this is already accomplished. The completion function
_sd_machines already lists the running containers.
Otherwise currently _available_machines is only used for machinectl
start.
see,
list*|cancel-transfer|pull-tar|pull-raw|pull-dkr)
msg=no options ;;
57 matches
Mail list logo
