On Fri, Jun 12, 2015 at 5:30 AM, Filipe Brandenburger
filbran...@google.com wrote:
On Thu, Jun 11, 2015 at 12:31 PM, Ronny Chevalier
chevalier.ro...@gmail.com wrote:
On Thu, Jun 11, 2015 at 6:31 PM, Filipe Brandenburger
filbran...@google.com wrote:
Another downside of adding comments to the
BTRFS_IOC_DEVICES_READY is to check if all the required devices
are known by the btrfs kernel, so that admin/system-application
could mount the FS. It is checked against a device in the argument.
However the actual implementation is bit more than just that,
in the way that it would also scan
On Sat, 23.05.15 13:04, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
It was a warning when we still supported kernel 3.4. current
minimum version is 3.7.
For the sake of the archives: this has been merged now as PR #76.
Lennart
--
Lennart Poettering, Red Hat
My host obtains an IP address and DNS server via DHCP from upstream via
Ethernet like this (systemd 219, Arch Linux)
[Match]
Name=en*
[Network]
DHCP=ipv4
It has the resolv.conf symlink to /run/systemd/resolve/resolv.conf, and the DNS
server from DHCP shows up there.
It also
В Fri, 12 Jun 2015 16:56:08 +0200
Francis Moreau francis.m...@gmail.com пишет:
On 06/11/2015 06:23 PM, Dan Williams wrote:
On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote:
[...]
Does ntpd service really need 'After=network.target', not sure.
The 'network online' targets are
On 06/11/2015 06:23 PM, Dan Williams wrote:
On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote:
[...]
Does ntpd service really need 'After=network.target', not sure.
The 'network online' targets are really just there for ignorant services
that don't respond to network events
On 25.03.2015 00:05, Tobias Hunger wrote:
Mount whatever the user asked to be mounted on / and /usr on the
kernel command line. Do less sanity check and do *not* bail out
when the mount device looks strange or does not exist.
This basically makes the changes for deviceless filesystems
from
Hi there,
is there a chance to pass (the given) environment variables down to
`unicorn` and `delayed_job-worker`?
systemd (host)
|
- docker-app.service
Environment=RAILS_ENV=production
Environment=DATABASE_URL=postgresql://localhost/app_development
|
Not sure I follow: why do this indirectly by killing nspawn?
Why not send this to the container init directly?
Note that if you know the nspawn PID, you can derive the external PID
of the init process easily by reading
/proc/$PID/task/$PID/children. It will only container one PID, and
On 06/12/2015 06:26 PM, Andrei Borzenkov wrote:
В Fri, 12 Jun 2015 16:56:08 +0200
Francis Moreau francis.m...@gmail.com пишет:
On 06/11/2015 06:23 PM, Dan Williams wrote:
On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote:
[...]
Does ntpd service really need 'After=network.target',
В Fri, 12 Jun 2015 21:16:30 +0800
Anand Jain anand.j...@oracle.com пишет:
BTRFS_IOC_DEVICES_READY is to check if all the required devices
are known by the btrfs kernel, so that admin/system-application
could mount the FS. It is checked against a device in the argument.
However the
11 matches
Mail list logo
