Hi Zbyszek,
On 27 May 2014 04:38, "Zbigniew Jędrzejewski-Szmek"
wrote:
>
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> > When enabled in [Network] it will set up a dhcp server on the
interface, listening
> > on one of its statically configured IPv4 addresses and with a fixed
2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>> When enabled in [Network] it will set up a dhcp server on the interface,
>> listening
>> on one of its statically configured IPv4 addresses and with a fixed size
>> pool of
On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
>> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its staticall
Hi
On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
>> before looking at the code, a couple of general questions:
>> - does the DHCP server have to be part of networkd? Isn't the job
>> of acquiring addresses and giving out address
On Tue, 27.05.14 04:38, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> > When enabled in [Network] it will set up a dhcp server on the interface,
> > listening
> > on one of its statically configured IPv4 addresses and
On Tue, 27.05.14 13:39, David Herrmann (dh.herrm...@gmail.com) wrote:
> Hi
>
> On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> > 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> >> before looking at the code, a couple of general questions:
> >> - does the DHCP server have to be
This causes the container to shut down cleanly when the service is
stopped.
---
units/systemd-nsp...@.service.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/units/systemd-nsp...@.service.in b/units/systemd-nsp...@.service.in
index ff36e90..6228345 100644
--- a/units/systemd-nsp...@.service
2014-05-27 14:00 GMT+02:00 Lennart Poettering :
>
> In many ways, if people complain about a dhcp server in networkd, then
> it's like complaining about the fact that pppd also can assign addresses
> to the other side...
I don't see pppd implementing a DHCP server.
--
Why is it that all of the i
On 21.05.2014 10:03, Lennart Poettering wrote:
> On Sun, 18.05.14 19:36, Przemek Rudy (pru...@o2.pl) wrote:
>
>> diff --git a/src/core/automount.c b/src/core/automount.c
>> index 65e6d6f..d4359b9 100644
>> --- a/src/core/automount.c
>> +++ b/src/core/automount.c
>> @@ -124,7 +124,7 @@ static int a
]] Lennart Poettering
> If we set up links (and especially, create them like
> we do for veth), then hel, yeah we should be prepared to make sure
> everybody gets an address on it.
Should we also include BGP, OSPF, RIP, ISIS (and their IPv6 variants) to
make sure it's possible to push routes?
Hi,
first of all I'd like to mark that I'm not sure if I'm writing in the
right place.
I have a problem with running a systemd service in "capability-only
environment": I want to run a process with some caps (cap_sys_admin
cap_dac_override cap_mac_override) as a regular user (UID != 0).
My
Hi,
On 27/05/14 13:50, Lennart Poettering wrote:
>> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its statically configured IPv4 addresses and with a fixed size
>>> pool of
On Mon, May 26, 2014 at 04:12:56PM +0800, WANG Chao wrote:
> Hi, all
>
> In a pure initramfs enviroment, I want to mount a filesystem and I put
> an mount entry in /etc/fstab, so that fstab-generator could generate a
> mount unit and systemd will mount it at some time.
>
> I have a question about
El 27/05/14 10:04, Eelco Dolstra escribió:
¿
That sounds reasonable. However, to be honest, I've never really understood why
networkd needs to be part of systemd in the first place.
For the start, to share a large amount code..
It seems to me that it
would work just as well as a separate pac
El 27/05/14 07:39, David Herrmann escribió:
> I strongly disagree. One major example is Wifi-P2P which requires a
> DHCP-Server for ad-hoc P2P connections.
OOk. that convinced me, thanks..
--
Cristian
"I don't know the key to success, but the key to failure is trying to
please everybody."
___
On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
> ]] Lennart Poettering
>
>> If we set up links (and especially, create them like
>> we do for veth), then hel, yeah we should be prepared to make sure
>> everybody gets an address on it.
>
> Should we also include BGP, OSPF, RIP, ISIS (and t
On Mon, May 26, 2014 at 09:39:37PM +0200, Tom Gundersen wrote:
> ---
> src/libsystemd-network/dhcp-server-internal.h | 1 +
> src/libsystemd-network/sd-dhcp-server.c | 13 +
> src/libsystemd-network/test-dhcp-server.c | 17 +
> src/systemd/sd-dhcp-server.h
On Tue, May 27, 2014 at 4:04 PM, Eelco Dolstra
wrote:
> However, to be honest, I've never really understood why
> networkd needs to be part of systemd in the first place. It seems to me that
> it
> would work just as well as a separate package with its own releases. To me as
> a
> downstream tha
On Tue, May 27, 2014 at 5:29 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Mon, May 26, 2014 at 09:39:37PM +0200, Tom Gundersen wrote:
>> ---
>> src/libsystemd-network/dhcp-server-internal.h | 1 +
>> src/libsystemd-network/sd-dhcp-server.c | 13 +
>> src/libsystemd-network/test-
I'm not sure this could be patch for below TODO.
* enabling an instance unit creates a pointless link, and
the unit will be started with getty@getty.service:
$ systemctl enable getty@.service
ln -s '/usr/lib/systemd/system/getty@.service'
'/etc/systemd/system/getty.target.wants/getty@.s
---
src/core/manager.c | 10 ++
src/shared/unit-name.c | 12
src/shared/unit-name.h | 1 +
3 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/src/core/manager.c b/src/core/manager.c
index 0cb2044..089df43 100644
--- a/src/core/manager.c
+++ b/src/core/manager
]] Tom Gundersen
> On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
> > ]] Lennart Poettering
> >
> >> If we set up links (and especially, create them like
> >> we do for veth), then hel, yeah we should be prepared to make sure
> >> everybody gets an address on it.
> >
> > Should we also
On Mon, May 26, 2014 at 09:39:39PM +0200, Tom Gundersen wrote:
> ---
> src/libsystemd-network/sd-dhcp-server.c | 81
> ++-
> src/libsystemd-network/test-dhcp-server.c | 14 +++---
> 2 files changed, 86 insertions(+), 9 deletions(-)
>
> diff --git a/src/libsystemd-ne
On 05/27/2014 03:20 PM, Tom Gundersen wrote:
On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
>]] Lennart Poettering
>
>>If we set up links (and especially, create them like
>>we do for veth), then hel, yeah we should be prepared to make sure
>>everybody gets an address on it.
>
>Shou
On Mon, May 26, 2014 at 09:39:40PM +0200, Tom Gundersen wrote:
> ---
> src/libsystemd-network/dhcp-server-internal.h | 3 +
> src/libsystemd-network/sd-dhcp-server.c | 135
> +-
> src/libsystemd-network/test-dhcp-server.c | 37 +++
> src/systemd/sd-dhcp-se
On Tue, May 27, 2014 at 5:48 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Mon, May 26, 2014 at 09:39:40PM +0200, Tom Gundersen wrote:
>> ---
>> src/libsystemd-network/dhcp-server-internal.h | 3 +
>> src/libsystemd-network/sd-dhcp-server.c | 135
>> +-
>> src/libsy
On Tue, May 27, 2014 at 5:41 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Mon, May 26, 2014 at 09:39:39PM +0200, Tom Gundersen wrote:
>> ---
>> src/libsystemd-network/sd-dhcp-server.c | 81
>> ++-
>> src/libsystemd-network/test-dhcp-server.c | 14 +++---
>> 2 files c
On Tue, May 20, 2014 at 5:07 AM, Cristian Rodríguez
wrote:
> ---
> Makefile.am | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/Makefile.am b/Makefile.am
> index f2a3bbd..bea3876 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -4195,6 +4195,8 @@ endif
>
> #
> ---
On Mon, May 26, 2014 at 09:39:43PM +0200, Tom Gundersen wrote:
> Make sure we don't hand out the same IP twice. We still don't
> handle lease expiry.
> ---
> src/libsystemd-network/dhcp-server-internal.h | 25 -
> src/libsystemd-network/sd-dhcp-server.c | 136
>
On Tue, May 27, 2014 at 05:33:34PM +0200, Tom Gundersen wrote:
> On Tue, May 27, 2014 at 5:29 PM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Mon, May 26, 2014 at 09:39:37PM +0200, Tom Gundersen wrote:
> >> ---
> >> src/libsystemd-network/dhcp-server-internal.h | 1 +
> >> src/libsystemd-network
On 05/27/2014 01:37 PM, Harald Hoyer wrote:
> On 21.05.2014 10:03, Lennart Poettering wrote:
>> On Sun, 18.05.14 19:36, Przemek Rudy (pru...@o2.pl) wrote:
>>
>>> diff --git a/src/core/automount.c b/src/core/automount.c
>>> index 65e6d6f..d4359b9 100644
>>> --- a/src/core/automount.c
>>> +++ b/src/c
>
> The container usecase alone is already the reason why I am so very sure
> I want this stuff, and that it needs to be in networkd, and just work. I
> want this fully automatic, so that we can create a hundred of veth
> tunnels, and trivially easy (simply by setting DHCPServer=yes for their
> .ne
On Tue, May 27, 2014 at 4:31 PM, Michal Witanowski
wrote:
> Hi,
>
> first of all I'd like to mark that I'm not sure if I'm writing in the right
> place.
>
> I have a problem with running a systemd service in "capability-only
> environment": I want to run a process with some caps (cap_sys_admin
> c
Quoting Mantas Mikulėnas (graw...@gmail.com):
> On Tue, May 27, 2014 at 4:31 PM, Michal Witanowski
> wrote:
> > Hi,
> >
> > first of all I'd like to mark that I'm not sure if I'm writing in the right
> > place.
> >
> > I have a problem with running a systemd service in "capability-only
> > environ
From: Thomas Hindoe Paaboel Andersen
Reuses logic from service.c and the rc-local generator.
Note that this drops reading of chkconfig entirely. It also drops reading
runlevels from the LSB headers. The runlevels were only used to check for
runlevels outside of the normal 1-5 range and then add
2014-05-28 1:12 GMT+02:00 Thomas H.P. Andersen :
> From: Thomas Hindoe Paaboel Andersen
>
> Reuses logic from service.c and the rc-local generator.
>
> Note that this drops reading of chkconfig entirely. It also drops reading
> runlevels from the LSB headers. The runlevels were only used to check
Am 27.05.2014 20:14, schrieb Kirill Elagin:
> The container usecase alone is already the reason why I am so very sure
> I want this stuff, and that it needs to be in networkd, and just work. I
> want this fully automatic, so that we can create a hundred of veth
> tunnels, and trivi
Hi,
I'm running Arch and recently upgraded system, now every time I boot I
see a dead service: rfkill1
systemd-rfkill@rfkill0.service loaded active
exitedLoad/Save RF Kill Switch Status of rfkill0
● systemd-rfkill@rfkill1.service loaded failed
failedL
El 27/05/14 20:14, Peeters Simon escribió:
> this feels wrong, the native unit should override the sysv one.
> Is there any reason why you want to change this?
> Couldn't you just use "arg_dest = argv[3];" instead?
>
This behaviour is probably my only objection to the idea in question,
the gener
Hi,
On Wed, 28 May 2014 08:25:52 +0800
Aaron Lewis wrote:
> Hi,
>
> I'm running Arch and recently upgraded system, now every time I boot I
> see a dead service: rfkill1
>
> systemd-rfkill@rfkill0.service loaded active
> exitedLoad/Save RF Kill Switch Status of rfkill0
>
On Wed, 12.02.14 09:46, Stef Walter (s...@thewalter.net) wrote:
heya!
I finally merged this patch. Sorry for the delay!
I wasn't sure about the rationale, but this appears to be the right
thing to do after all, so I merged it!
Thank you!
Lennart
> It is almost always incorrect to allow DHCP o
On Wed, May 28, 2014 at 01:12:23AM +0200, Thomas H.P. Andersen wrote:
> From: Thomas Hindoe Paaboel Andersen
>
> Reuses logic from service.c and the rc-local generator.
>
> Note that this drops reading of chkconfig entirely.
How likely is this to cause regressions in existing distributions?
>
On Tue, 27.05.14 14:28, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2014-05-27 14:00 GMT+02:00 Lennart Poettering :
> >
> > In many ways, if people complain about a dhcp server in networkd, then
> > it's like complaining about the fact that pppd also can assign addresses
> > to the other side...
On Tue, 27.05.14 16:04, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
> > I am very sure this should be in networkd.
> [snip]
>
> That sounds reasonable. However, to be honest, I've never really understood
> why
> networkd needs to be part of systemd in the first place. It seems to
> me th
Works, Thanks Leonid
On Wed, May 28, 2014 at 8:35 AM, Leonid Isaev wrote:
> Hi,
>
> On Wed, 28 May 2014 08:25:52 +0800
> Aaron Lewis wrote:
>
>> Hi,
>>
>> I'm running Arch and recently upgraded system, now every time I boot I
>> see a dead service: rfkill1
>>
>> systemd-rfkill@rfkill0.service
One of the cleanest ways to do what you want is to create a
D-Bus-activated systemd service (or socket-activated, if that's more
appropriate). That allows activation completely outside the user's
session without elevated privileges. Of course, it requires
considerable work for each service to do it
Is there a downside to using KillMode=mixed instead?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 28 May 2014 13:36, David Timothy Strauss wrote:
> Is there a downside to using KillMode=mixed instead?
I suspect one downside is that if the container takes longer than the
timeout to shutdown then it will go on a SIGKILL-ing spree... which
could be a problem if a container process was in the
On Tue, May 27, 2014 at 10:55 PM, Jonathan Liu wrote:
> I suspect one downside is that if the container takes longer than the
> timeout to shutdown then it will go on a SIGKILL-ing spree... which
> could be a problem if a container process was in the middle of saving
> to disk while shutting down.
On May 28, 2014 3:25 AM, "Aaron Lewis" wrote:
>
> Hi,
>
> I'm running Arch and recently upgraded system, now every time I boot I
> see a dead service: rfkill1
>
> systemd-rfkill@rfkill0.service loaded active
> exitedLoad/Save RF Kill Switch Status of rfkill0
> ● systemd-rfk
50 matches
Mail list logo