This might be due to trying to use systemd-nspawn -x with a raw image
inside the btrfs /var/lib/machines volume. It doesn't work in the
sense that the container isn't ephemeral, but there's no error message
either, and this leftover gets created.
If I jump through elaborate hoops to create the co
On Fri, 04.11.16 11:12, c...@endlessnow.com (c...@endlessnow.com) wrote:
>
> >On Thu, Nov 03, 2016 at 04:01:15PM -0700, c...@endlessnow.com wrote:
> >> so I'm using CentOS 7, and we're mounting a disk from our
> iSCSI
> >> SAN and then we want to export that via NFS. But on a fresh boot
>
On Fri, 04.11.16 16:14, Marc Haber (mh+systemd-de...@zugschlus.de) wrote:
> On Thu, Nov 03, 2016 at 10:55:35PM +0100, Lennart Poettering wrote:
> > On Mon, 26.09.16 07:02, Marc Haber (mh+systemd-de...@zugschlus.de) wrote:
> > > On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote:
> > > >
On Thu, Nov 03, 2016 at 10:55:35PM +0100, Lennart Poettering wrote:
> On Mon, 26.09.16 07:02, Marc Haber (mh+systemd-de...@zugschlus.de) wrote:
> > On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote:
> > > The emergency mode assumes console access, which requires physical access,
> > > w
Hello Michal,
Michal Privoznik [2016-11-04 8:47 +0100]:
> That means that whenever a VM is being started up, libvirtd (our
> daemon we have) relabels all the necessary paths that QEMU process
> (representing VM) can touch.
Does that mean it's shipping an udev rule that does that? Or actually
lis
>On Thu, Nov 03, 2016 at 04:01:15PM -0700, c...@endlessnow.com wrote:
>> so I'm using CentOS 7, and we're mounting a disk from our
iSCSI
>> SAN and then we want to export that via NFS. But on a fresh boot
the
>> nfs-server service fails because the filesytem isn't there yet.
Any
>> ideas
Am 04.11.2016 um 16:26 schrieb Cecil Westerhof:
2016-11-04 15:46 GMT+01:00 Cecil Westerhof :
I want to set my own keyboard definitions when they get lost. They
sometimes do. The only way of doing this automatically is in a cronjob
or a systemd service. I would prefer a systemd service. But for
2016-11-04 15:46 GMT+01:00 Cecil Westerhof :
> I want to set my own keyboard definitions when they get lost. They
> sometimes do. The only way of doing this automatically is in a cronjob
> or a systemd service. I would prefer a systemd service. But for the
> moment I rewrite the script to be run fr
2016-11-04 13:29 GMT+01:00 Mantas Mikulėnas :
> On Fri, Nov 4, 2016 at 1:47 PM, Cecil Westerhof
> wrote:
>>
>> I have a script I want to run as a service which uses:
>> xmodmap -pk
>> I have to define the DISPLAY, so I use:
>> export DISPLAY=:0.0
>>
>> But this gives:
>> export DISPLAY
On Fri, 04.11.16 09:38, Bjørn Forsman (bjorn.fors...@gmail.com) wrote:
> Hi Lennart,
>
> On 3 November 2016 at 20:19, Lennart Poettering
> wrote:
> > Your mail does not say in any way what precisely your issue is?
>
> Did you read the first post? I hope not, because I don't really know
> how t
On Fri, 04.11.16 12:47, Cecil Westerhof (cldwester...@gmail.com) wrote:
> I have a script I want to run as a service which uses:
> xmodmap -pk
> I have to define the DISPLAY, so I use:
> export DISPLAY=:0.0
>
> But this gives:
> export DISPLAY=:0.0
> xmodmap: unable to open displ
On Fri, Nov 4, 2016 at 1:47 PM, Cecil Westerhof
wrote:
> I have a script I want to run as a service which uses:
> xmodmap -pk
> I have to define the DISPLAY, so I use:
> export DISPLAY=:0.0
>
> But this gives:
> export DISPLAY=:0.0
> xmodmap: unable to open display ':0.0'
>
> Whe
On Tue, 20 Sep 2016, Bjørn Forsman wrote:
Hi systemd developers,
My name is Bjørn Forsman and this is my first post to this list. I
have a question/issue with the behaviour of (auto)mount units.
When a mount unit fails (repeatedly), it takes the corresponding
automount unit down with it. To me
I have a script I want to run as a service which uses:
xmodmap -pk
I have to define the DISPLAY, so I use:
export DISPLAY=:0.0
But this gives:
export DISPLAY=:0.0
xmodmap: unable to open display ':0.0'
When I try the same with at, I do not have this problem.
What is happening he
On Thu, Nov 03, 2016 at 04:01:15PM -0700, c...@endlessnow.com wrote:
> so I'm using CentOS 7, and we're mounting a disk from our iSCSI
> SAN and then we want to export that via NFS. But on a fresh boot the
> nfs-server service fails because the filesytem isn't there yet. Any
> ideas on how to
so I'm using CentOS 7, and we're mounting a disk from our iSCSI
SAN and then we want to export that via NFS. But on a fresh boot the
nfs-server service fails because the filesytem isn't there yet. Any
ideas on how to fix this?
___
systemd-devel ma
Hi Lennart,
On 3 November 2016 at 20:19, Lennart Poettering wrote:
> Your mail does not say in any way what precisely your issue is?
Did you read the first post? I hope not, because I don't really know
how to describe it more precisely than that :-)
Below is a copy of the first post.
When a mo
Hey udev developers,
I'm a libvirt developer and I've been facing an interesting issue
recently. Libvirt is a library for managing virtual machines and as such
allows basically any device to be exposed to a virtual machine. For
instance, a virtual machine can use /dev/sdX as its own disk. Because
Hi,
Thx for the reply.
> We had an issue with that in the past, please retry with a less ancient
> version of systemd, I am pretty sure this was already fixed, but I can't tell
> you really when precisely.
This is most probably not possible for the project in this state. I'll try to
find the
19 matches
Mail list logo
