On Tue, 08.09.15 22:57, Alexey Shabalin (a.shaba...@gmail.com) wrote:
> 2015-09-08 16:32 GMT+03:00 David Herrmann :
>
> > Hi
> >
> > Here's the next version of systemd, v226:
> > * nspawn learnt support for .nspawn settings files, that may
> > accompany the image files or direct
On 9/9/2015 PM 02:11, Lennart Poettering wrote:
On Wed, 09.09.15 10:50, Steven Shiau (ste...@nchc.org.tw) wrote:
On 9/8/2015 PM 10:05, Lennart Poettering wrote:
On Tue, 08.09.15 20:45, Steven Shiau (ste...@nchc.org.tw) wrote:
Dear systemd developers,
I encountered a very weird issue, i.e.
On Wed, 09.09.15 10:50, Steven Shiau (ste...@nchc.org.tw) wrote:
>
> On 9/8/2015 PM 10:05, Lennart Poettering wrote:
> >On Tue, 08.09.15 20:45, Steven Shiau (ste...@nchc.org.tw) wrote:
> >
> >>Dear systemd developers,
> >>I encountered a very weird issue, i.e. the /dev or /tmp disappears when
> >
On 9/8/2015 PM 10:05, Lennart Poettering wrote:
On Tue, 08.09.15 20:45, Steven Shiau (ste...@nchc.org.tw) wrote:
Dear systemd developers,
I encountered a very weird issue, i.e. the /dev or /tmp disappears when
program is running.
The client system is nfsroot (diskless), running on the Debian S
Hi Lennart,
On 09/06/2015 05:48 AM, Lennart Poettering wrote:
On Fri, 04.09.15 10:59, David Milburn (dmilb...@redhat.com) wrote:
Please file this issue as github PR:
https://github.com/systemd/systemd
Ok, did that.
+static struct udev_device *handle_scsi_ata(struct udev_device *parent,
2015-09-08 16:32 GMT+03:00 David Herrmann :
> Hi
>
> Here's the next version of systemd, v226:
> * nspawn learnt support for .nspawn settings files, that may
> accompany the image files or directories of containers, and
> may contain additional settings for the containe
On 08/09/15 13:55, Francis Moreau wrote:
> On 09/08/2015 12:09 PM, Richard Maw wrote:
>> I understood that the common configuration for socket activated sshd was to
>> have a sshd.service for if you want it to always be running, and a pair of
>> sshd@.service and sshd.socket.
>
> Ah no, with this
Hi,
With systemd 225 on an archlinux, I cannot override a nspawn service anymore.
Example:
One container named ci-container, declared as this :
# ls -al /etc/systemd/system/machines.target.wants/
total 8
drwxr-xr-x 2 root root 4096 8 sept. 16:06 .
drwxr-xr-x 8 root root 4096 8 sept. 16:06 ..
lr
- Original Message -
> From: "Lennart Poettering"
> To: "Yeela Kaplan"
> Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali" ,
> "Dan Kenigsberg"
> Sent: Tuesday, September 8, 2015 6:51:30 PM
> Subject: Re: [systemd-devel] Cannot start service due to
> 'systemd-tty-ask-password-a
On Tue, 08.09.15 11:29, Yeela Kaplan (ykap...@redhat.com) wrote:
> > Hmm? You wrote earlier that systemctl was hanging. Is it hanging or
> > isn't it hanging?
>
> I'm sorry, I used the wrong word.
> I meant that it is not blocking.
> But it also does not start the service.
> So eventually, that'
- Original Message -
> From: "Lennart Poettering"
> To: "Yeela Kaplan"
> Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali" ,
> "Dan Kenigsberg"
> Sent: Tuesday, September 8, 2015 6:23:56 PM
> Subject: Re: [systemd-devel] Cannot start service due to
> 'systemd-tty-ask-password-a
On Tue, 08.09.15 10:47, Yeela Kaplan (ykap...@redhat.com) wrote:
>
>
> - Original Message -
> > From: "Lennart Poettering"
> > To: "Yeela Kaplan"
> > Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali" ,
> > "Dan Kenigsberg"
> > Sent: Tuesday, September 8, 2015 4:48:31 PM
> > Sub
- Original Message -
> From: "Lennart Poettering"
> To: "Yeela Kaplan"
> Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali" ,
> "Dan Kenigsberg"
> Sent: Tuesday, September 8, 2015 4:48:31 PM
> Subject: Re: [systemd-devel] Cannot start service due to
> 'systemd-tty-ask-password-a
On Tue, Sep 08, 2015 at 04:14:58PM +0200, Michał Zegan wrote:
> Hello.
>
> Before you stated that containers are not a security feature right
> now. It is required to manually shift uids/gids on images etc.
Yes.
Also, if you uid-shift the container's root directory, using `--private-users`
witho
Hello.
Before you stated that containers are not a security feature right now.
It is required to manually shift uids/gids on images etc.
What are other known problems with containers that use ALL namespaces?
Like if not counting the problem of uid allocation and manual shifting
of them.
_
Hi all,
I was looking into how the $network LSB facility name was handled by
systemd-sysv-generator, in particular with its interaction with
network-pre.target. I think the generator might be missing a couple of
cases.
Currently we have "Provides: $network" translated into:
Before=network
On Tue, 08.09.15 20:45, Steven Shiau (ste...@nchc.org.tw) wrote:
> Dear systemd developers,
> I encountered a very weird issue, i.e. the /dev or /tmp disappears when
> program is running.
> The client system is nfsroot (diskless), running on the Debian Sid with
> Linux kernel 4.1.0-2-amd64. The PX
On Tue, 08.09.15 07:56, Yeela Kaplan (ykap...@redhat.com) wrote:
> > > Thank you for your response.
> > > I have tried running: strace -f systemctl --no-ask-password start
> > > supervdsmd.service
> > > and it still reproduces.
> > > but now intead of:
> > > bash(3448)─┬─pstree(3625)
> > >
Hi
Here's the next version of systemd, v226:
https://github.com/systemd/systemd/archive/v226.tar.gz
As usual, many bug-fixes and cleanups, but also a rather large set of
new features this time, including support for unified cgroups, many
DHCP improvements, extensions to the polkit integratio
On 09/08/2015 12:09 PM, Richard Maw wrote:
> On Tue, Sep 08, 2015 at 10:05:05AM +0200, Francis Moreau wrote:
>> On 09/07/2015 11:28 AM, Richard Maw wrote:
>>> On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote:
How is this handled ? Should we put a big warning in sshd_config to hin
Dear systemd developers,
I encountered a very weird issue, i.e. the /dev or /tmp disappears when
program is running.
The client system is nfsroot (diskless), running on the Debian Sid with
Linux kernel 4.1.0-2-amd64. The PXE/NFS server is a Debian Live system
running NFS server by unfs3 [1], its mo
- Original Message -
> From: "Lennart Poettering"
> To: "Yeela Kaplan"
> Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali" ,
> "Dan Kenigsberg"
> Sent: Tuesday, September 8, 2015 1:45:54 PM
> Subject: Re: [systemd-devel] Cannot start service due to
> 'systemd-tty-ask-password-a
On Tue, 08.09.15 05:51, Yeela Kaplan (ykap...@redhat.com) wrote:
> > This is really a misconception about what
> > systemd-tty-ask-password-agent actually does. It's job is to bring
> > password queries from system components to the screen while you wait
> > for systemctl to finish. This is useful
On Tue, Sep 08, 2015 at 10:05:05AM +0200, Francis Moreau wrote:
> On 09/07/2015 11:28 AM, Richard Maw wrote:
> > On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote:
> >> How is this handled ? Should we put a big warning in sshd_config to hint
> >> user to configure ListenAddress in sshd
- Original Message -
> From: "Lennart Poettering"
> To: "Yeela Kaplan"
> Cc: systemd-devel@lists.freedesktop.org, "Oved Ourfali"
> Sent: Sunday, September 6, 2015 4:56:29 PM
> Subject: Re: [systemd-devel] Cannot start service due to
> 'systemd-tty-ask-password-agent --watch' not answe
Hello,
On a fresh boot (no /etc/machine-id yet), I'm getting:
systemd[1]: Failed to populate /etc with preset unit settings, ignoring: File
exists
The files that systemd is complaining about are installed by systemd
itself (/etc/systemd/system/getty.target.wants/getty@tty1.service and
/etc/system
On 09/07/2015 11:28 AM, Richard Maw wrote:
> On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote:
>> How is this handled ? Should we put a big warning in sshd_config to hint
>> user to configure ListenAddress in sshd.socket in the case socket
>> activation is used ?
>
>> Or should sshd
Am 09/08/2015 um 08:51 AM schrieb Daurnimator:
> On 8 September 2015 at 16:16, Daniel Spannbauer wrote:
>> Can I test the system without rebooting it to
>> find ordering cycles?
> Try `systemd-analyze verify myfile.someunit`
Hmmm, this works only for one service. Can I also analyze the whole
syste
28 matches
Mail list logo