---
configure.ac | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configure.ac b/configure.ac
index 90aa3cc..76d2119 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1442,6 +1442,8 @@ AC_MSG_RESULT([
SysV compatibility: ${SYSTEM_SYSV_COMPAT}
compatibility libraries: ${h
Hi
On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams wrote:
> On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
>> systemd tries to launch logind service which now waits for services it
>> is ordered After and eventually times out.
>
> NM patch filed for review by NM dev team:
>
> https://bu
Unlike the case with a network capable scanner i.e. the scanner connected
directly to the network,
these are the settings for sharing across a network scanner connected to a
computer via USB.
As root, on *server*:
1. Create 'saned' user & group
# getent group saned >/dev/null 2>&1 || groupad
On Tue, Oct 21, 2014 at 10:55:46PM +0200, Ronny Chevalier wrote:
> >> >> +if (arg_transport != BUS_TRANSPORT_LOCAL) {
> >> >> +log_error("Cannot remotely edit units");
> >> >> +return -EINVAL;
> >> >> +}
> >> >> +
> >> >> +if (arg_runtime) {
>
On Sun, Dec 14, 2014 at 04:21:32PM +0300, Ivan Shapovalov wrote:
> On Saturday 13 December 2014 at 15:34:01, Ronny Chevalier wrote:
> > 2014-12-13 11:33 GMT+01:00 Ivan Shapovalov :
> > > Hello all,
> >
> > Hi,
> >
> > >
> > > it seems that the newly added `systemctl edit` command requires i
On Mon, Dec 15, 2014 at 11:34:24AM +0100, har...@redhat.com wrote:
> From: Harald Hoyer
>
> "gateway." skips adding the domain search path and saves some queries to
> the nameserver.
Pushed it... Works nicely and seems useful.
Zbyszek
___
systemd-devel
On Mon, Dec 15, 2014 at 10:39:00AM +0100, Jan Synacek wrote:
> ---
> src/systemctl/systemctl.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
> index 8400bc8..91e8f7c 100644
> --- a/src/systemctl/systemctl.c
> +++
On Tue, Dec 16, 2014 at 08:48:34AM +0530, Susant Sahani wrote:
> src/shared/utf8.c:268:13: warning: unused variable 'd'
> [-Wunused-variable]
> int d;
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lis
Hi,
> On Monday, 15 December 2014 10:54 PM, P J P wrote:
> and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0. I
> have hit
># shutdown -r now
>and boot-up has stalled at the same spot again. Let's see...
On a VM I had enabled 'CONFIG_LOCKUP_DETECTOR=y' & 'CONFIG_DE
src/shared/utf8.c:268:13: warning: unused variable 'd'
[-Wunused-variable]
int d;
---
src/shared/utf8.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/shared/utf8.c b/src/shared/utf8.c
index 67f6285..03a0abe 100644
--- a/src/shared/utf8.c
+++ b/src/shared/utf8.c
@@ -265,7 +265,6 @
Hello-
How is a user supposed to disable DefaultDependencies on a scope? From
the docs it seems like it should work:
"Unless DefaultDependencies=false is used, scope units will implicitly
have dependencies of type Conflicts= and Before= on shutdown.target."
But, in practice:
systemd-run --scope
Hello!
I'm seeing the following errors in systemd's journal:
Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session):
Could not set limit for 'memlock': Operation not permitted
Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session):
Could not set limit for 'nice
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
> В Mon, 15 Dec 2014 11:34:17 -0600
> Dan Williams пишет:
>
> >
> > On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> > > On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> > >
> > > > NetworkManager se
Hi Alin,
Thanks for the patch!
Overall it looks excellent, my only concern is with the clearing of
FDB entries. Is there any reason to treat this differently than how we
currently treat routes and addresses?
The current logic is that we don't support run-time reconfiguration
(we only apply our (
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams пишет:
>
> On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> > On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> >
> > > NetworkManager sets logind inhibitor lock to monitor for suspend
> > > events. So it implici
On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
> On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> > NetworkManager sets logind inhibitor lock to monitor for suspend
> > events. So it implicitly requires logind to be present when NM
> > starts.
NM doesn't ac
On Mon, 15.12.14 08:01, Ken Werner (k...@linux.vnet.ibm.com) wrote:
> From: Ken Werner
>
> Since the order of the first and second arguments of the raw clone()
> system call is reversed on s390 and cris it needs to be invoked differently.
>
> Signed-off-by: Ken Werner
Hmm, I'd prefer if we co
Hi,
> On Monday, 15 December 2014 9:23 PM, Lennart Poettering wrote:
> Can you boot with "systemd.log_level=debug systemd.log_target=kmsg"?
> This should print all logs to the console.
Yes done! -> http://fpaste.org/159929/
> Most likely there's some necessary kernel option not enabled in y
From: Ken Werner
Hi there,
It appears that systemd-nspawn doesn't work on s390 (and cris probably). The
clone() fails because the signature of the raw system call is slightly
different on these architectures. Since the order of the first and second
arguments is reversed it gets invoked with a
From: Ken Werner
Since the order of the first and second arguments of the raw clone()
system call is reversed on s390 and cris it needs to be invoked differently.
Signed-off-by: Ken Werner
---
src/nspawn/nspawn.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/s
On Mon, 15.12.14 11:45, P J P (p...@fedoraproject.org) wrote:
>Hello,
>
> Please see:
> -> http://fpaste.org/159783/
> ->
> https://lists.fedoraproject.org/pipermail/devel/2014-September/202289.html
>
> I first encountered this issue with a custom built kernel-3.16,
> then in kernel-3.1
On Mon, Dec 15, 2014 at 5:40 PM, Lennart Poettering
wrote:
>
> On Sat, 13.12.14 08:32, Matthias Urlichs (matth...@urlichs.de) wrote:
>
> > Hi,
> >
> > Zbigniew Jędrzejewski-Szmek:
> > > > wrap a few *_FOREACH macros in curly braces
> > > >
> > > cppcheck is full of errors anyway. I don't think
On Mon, Dec 15, 2014 at 04:36:51PM +0100, Lennart Poettering wrote:
> On Sun, 14.12.14 19:12, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > Otherwise this actually remains in the generated unit in /usr/lib.
> >
> > If you want to keep it commented out, a m4-compatible way would be:
> >
> >
On Sat, 13.12.14 08:32, Matthias Urlichs (matth...@urlichs.de) wrote:
> Hi,
>
> Zbigniew Jędrzejewski-Szmek:
> > > wrap a few *_FOREACH macros in curly braces
> > >
> > cppcheck is full of errors anyway. I don't think we should make the code
> > less pretty just to satisfy a checker, and
On Sun, 14.12.14 19:12, Mantas Mikulėnas (graw...@gmail.com) wrote:
> Otherwise this actually remains in the generated unit in /usr/lib.
>
> If you want to keep it commented out, a m4-compatible way would be:
>
> m4_ifdef(`HAVE_SMACK',
> dnl Capabilities=cap_mac_admin=i
> dnl SecureB
On 12/15/2014 03:15 PM, P J P wrote:
On Monday, 15 December 2014 6:43 PM, Jóhann B. Guðmundsson wrote:
It's not irrelevant since you might not be compiling your kernel without
required config options which either break dracut or systemd.
Is there a known list of these options that a user mu
> On Monday, 15 December 2014 6:43 PM, Jóhann B. Guðmundsson wrote:
> It's not irrelevant since you might not be compiling your kernel without
> required config options which either break dracut or systemd.
Is there a known list of these options that a user must enable?
---
Regards
-P J P
On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> NetworkManager sets logind inhibitor lock to monitor for suspend
> events. So it implicitly requires logind to be present when NM
> starts.
Any idea what it needs the inhibitor for?
> logind is ordered after nss-user-lookup.
Hi
On Mon, Dec 15, 2014 at 1:08 PM, Martin Pitt wrote:
> Martin Pitt [2014-12-15 12:50 +0100]:
>> #7 0x5659c185 in time_get_dst (date=1418644009, tzfile=0x5659e9ee
>> "/etc/localtime", switch_cur=0xd81c, zone_cur=0xd810,
>> dst_cur=0xd809, switch_next=0xd824, delta_next=0xff
Hi
On Mon, Dec 15, 2014 at 11:26 AM, wrote:
> From: Harald Hoyer
>
> ---
> hwdb/70-mouse.hwdb | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/hwdb/70-mouse.hwdb b/hwdb/70-mouse.hwdb
> index 36778d5..06b5338 100644
> --- a/hwdb/70-mouse.hwdb
> +++ b/hwdb/70-mouse.hwdb
> @@ -168,6 +
On 12/15/2014 12:32 PM, P J P wrote:
It does not happen there. Though IMO that's irrelevant.
It's not irrelevant since you might not be compiling your kernel without
required config options which either break dracut or systemd.
JBG
___
systemd-
Hi
On Sat, Dec 13, 2014 at 5:34 PM, Léo Gillot-Lamure
wrote:
> Hi.
>
> I want to give ownership of a particular sound card to a specific user
> permanently, so that 1/ I have a guarantee that other users' sessions
> can not emit sound on this card and 2/ the sound playing on the
> specific users'
15.12.2014 14:31, Hannes Reinecke wrote:
Hi all,
in commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
(udev: serialize/synchronize block device event handling with file
locks) udev started using flock() on the device node, supposedly to
synchronize with an ominous 'block event handling'.
This is
> On Monday, 15 December 2014 5:40 PM, Jóhann B. Guðmundsson wrote:
> Start by Installing and trying the Fedora stock kernel to see if it
> happens there then report back here.
It does not happen there. Though IMO that's irrelevant.
I left the VM with the custom 3.18.0 kernel in the stalled s
On 12/15/2014 12:02 PM, P J P wrote:
On Monday, 15 December 2014 5:24 PM, Jóhann B. Guðmundsson wrote:
Do you encounter this with none custom built kernel in Fedora?
I don't use the Fedora kernel, so I haven't seen it there. But as said earlier,
Paul I guess encountered it with the Fedora kern
Martin Pitt [2014-12-15 12:50 +0100]:
> #7 0x5659c185 in time_get_dst (date=1418644009, tzfile=0x5659e9ee
> "/etc/localtime", switch_cur=0xd81c, zone_cur=0xd810,
> dst_cur=0xd809, switch_next=0xd824, delta_next=0xd820,
> zone_next=0xd814, dst_next=0xd80a)
> a
> On Monday, 15 December 2014 5:24 PM, Jóhann B. Guðmundsson wrote:
> Do you encounter this with none custom built kernel in Fedora?
I don't use the Fedora kernel, so I haven't seen it there. But as said earlier,
Paul I guess encountered it with the Fedora kernel
-> https://lists.fedoraprojec
On 12/15/2014 11:45 AM, P J P wrote:
I first encountered this issue with a custom built kernel-3.16,
then in kernel-3.17 and now in 3.18
Do you encounter this with none custom built kernel in Fedora?
JBG
___
systemd-devel mailing list
systemd-devel@
Hey Tom, all,
with systemd 218 our integration tests picked out a regression with
timedatectl: just calling it without any arguments crashes with
*** Error in `./timedatectl': free(): invalid next size (fast): 0xf8cce8d8 ***
I only get this crash on i386 (32 bit), not x86_64. It also only
happ
Hello,
Please see:
-> http://fpaste.org/159783/
-> https://lists.fedoraproject.org/pipermail/devel/2014-September/202289.html
I first encountered this issue with a custom built kernel-3.16,
then in kernel-3.17 and now in 3.18 too. First issue here is that
kernel boot-up halts after saying
From: Harald Hoyer
"gateway." skips adding the domain search path and saves some queries to
the nameserver.
---
src/nss-myhostname/nss-myhostname.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/nss-myhostname/nss-myhostname.c
b/src/nss-myhostname/nss-myhostname.c
i
From: Harald Hoyer
---
hwdb/70-mouse.hwdb | 4
1 file changed, 4 insertions(+)
diff --git a/hwdb/70-mouse.hwdb b/hwdb/70-mouse.hwdb
index 36778d5..06b5338 100644
--- a/hwdb/70-mouse.hwdb
+++ b/hwdb/70-mouse.hwdb
@@ -168,6 +168,10 @@ mouse:usb:v046dpc52b:name:Logitech Unifying Device.
Wire
Signed-off-by: Alin Rauta
---
Makefile.am | 1 +
man/systemd.network.xml | 22 ++
src/libsystemd/sd-rtnl/rtnl-message.c| 56 -
src/libsystemd/sd-rtnl/rtnl-types.c | 15 +-
src/network/networkd-fdb.c | 357 ++
Hi,
Based on your feedback, I've created a new patch for adding the FDB support.
networkd takes ownership of the FDB table.
Configuration example:
> cat /etc/systemd/network/em1.network
[Match]
Name=em1
[Network]
DHCP=v4
[BridgeFDB]
MACAddress=04:44:12:34:56:70
VLAN=2
[BridgeFDB]
MACAddress=
---
src/systemctl/systemctl.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 8400bc8..91e8f7c 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@ -6942,7 +6942,7 @@ static int shutdown_parse_a
Hi all,
in commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
(udev: serialize/synchronize block device event handling with file
locks) udev started using flock() on the device node, supposedly to
synchronize with an ominous 'block event handling'.
The code looks like this:
if (d)
46 matches
Mail list logo
