On Sat, Feb 7, 2015 at 3:38 PM, Thomas H.P. Andersen pho...@gmail.com wrote:
On Sat, Feb 7, 2015 at 2:37 PM, Ronny Chevalier
chevalier.ro...@gmail.com wrote:
2015-02-07 14:05 GMT+01:00 Daniele Nicolodi dani...@grinta.net:
On 07/02/15 10:29, Thomas H.P. Andersen wrote:
I am looking at ways to
This patch fixes also problem with ReleaseName call in
systemd-bus-proxyd.
diff --git a/names.c b/names.c
index 5f57aa3..e85ba45 100644
--- a/names.c
+++ b/names.c
@@ -266,6 +266,7 @@ static int kdbus_name_release(struct kdbus_name_registry
*reg,
* for items for connection.
On Mon, Feb 09, 2015 at 03:06:46AM -0800, Alin Rauta wrote:
---
man/systemd.network.xml | 11 ++
src/libsystemd/sd-network/sd-network.c | 4 +
src/network/networkctl.c | 212
---
src/network/networkd-link.c |
Hi,
With the systemd init manager,not able to get the login prompt despite all
required services are started.All the relevant logs are pasted.
Kindly help in finding the root cause.
i have tried passing systemd.unit=rescue.target to the kernel and i can see
the login prompt.
But not able to login
Issue fixed by setting the Linux kernel configuration item CONFIG_FHANDLE.
Thanks,
Avinash
On Mon, Feb 9, 2015 at 6:30 PM, avinash nalluri avinash.nall...@gmail.com
wrote:
Hi,
With the systemd init manager,not able to get the login prompt despite all
required services are started.All the
В Mon, 9 Feb 2015 19:25:34 +1100
Adam Zegelin a...@instaclustr.com пишет:
Hi list,
Is the following expected behaviour?
Given services A, B, and C.
C Requires A B.
All units are inactive.
`systemctl restart A` activates C, which in turn activates B.
Whereas `systemctl start A`
Hi list,
Is the following expected behaviour?
Given services A, B, and C.
C Requires A B.
All units are inactive.
`systemctl restart A` activates C, which in turn activates B.
Whereas `systemctl start A` activates A and only A. C and B are left inactive.
I can understand that starting C
Lennart Poettering lenn...@poettering.net schrieb:
On Mon, 15.12.14 22:42, Kai Krakow (hurikha...@gmail.com) wrote:
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':
Hello there! I just wanted to ask about the sealing log feature because I can't
make it work. I tried to set it up in the following way:
I stopped the journald service:
root:/var/log/journal/159815709bbc46c29ef786cfc497afd4# systemctl stop
systemd-journald-dev-log.socket
I'm playing with the journal to see what useful things it can do, and I
have two questions:
1. Rsyslog has the ability of filtering logs, for instance:
if $syslogtag contains something and ($msg contains something-else or $msg
contains something-different) then -/var/log/trash.log
or something
On 02/09/2015 10:53 AM, Lukasz Skalski wrote:
This patch fixes also problem with ReleaseName call in
systemd-bus-proxyd.
Applied, thanks!
diff --git a/names.c b/names.c
index 5f57aa3..e85ba45 100644
--- a/names.c
+++ b/names.c
@@ -266,6 +266,7 @@ static int kdbus_name_release(struct
On Mon, Feb 9, 2015 at 3:56 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Mon, Feb 09, 2015 at 03:20:35AM -0800, Tom Gundersen wrote:
man/systemd.network.xml |8 +--
network/80-container-host0.network |2
network/80-container-ve.network |
first asked here: http://stackoverflow.com/questions/28399754
I've setup my home server to wake-on-lan and my router sends the wake-on-lan
package when I try to access the server from anywhere.
Now the server should also suspend again after like 5 minutes after
- last disk activity
-
---
man/systemd.network.xml | 11 ++
src/libsystemd/sd-network/sd-network.c | 4 +
src/network/networkctl.c | 212 ---
src/network/networkd-link.c | 178 ++
src/network/networkd-link.h
Hi,
I've added Uplink failure detection support through BindCarrier= flag.
Please let me know what you think.
/Alin
Alin Rauta (1):
Added support for Uplink Failure Detection using BindCarrier
man/systemd.network.xml | 11 ++
src/libsystemd/sd-network/sd-network.c | 4
On Thu, 5 Feb 2015 14:19:35 +0100
Robert Milasan rmila...@suse.com wrote:
Signed-off-by: Robert Milasan rmila...@suse.com
---
src/udev/ata_id/ata_id.c | 4
1 file changed, 4 deletions(-)
diff --git a/src/udev/ata_id/ata_id.c b/src/udev/ata_id/ata_id.c
index 31bc167..9e4f674 100644
On 10 Feb 2015, at 6:46 am, Andrei Borzenkov arvidj...@gmail.com wrote:
B is started because C is started so it is not relevant.
Yes, this is expected because B is a dependency of C. Starting C should start B.
I mentioned it because, to me, it was unexpected that /re/starting A caused B
to
Hey Torstein,
thanks! Committed with slightly normalized description:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=e2acdb6
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
On Sunday 08 February 2015 16:52:47 Zbigniew Jędrzejewski-Szmek wrote:
Seriously, what's the point? All this complications to save a minute
or two of compile time?
thanks for the hint
everythinng is now OK
however I found hard links to /usr/lib even when when passes
--libexecdir=/usr/lib64 for
---
man/systemd.link.xml | 2 +-
man/systemd.unit.xml | 2 +-
src/libsystemd-network/dhcp-identifier.c | 2 +-
src/libsystemd-network/dhcp-network.c| 2 +-
src/libsystemd-network/sd-dhcp-server.c | 2 +-
src/network/networkd-link.c | 2 +-
On Mon, Feb 09, 2015 at 03:20:35AM -0800, Tom Gundersen wrote:
man/systemd.network.xml |8 +--
network/80-container-host0.network |2
network/80-container-ve.network |2
src/libsystemd/sd-rtnl/rtnl-types.c | 19 ---
21 matches
Mail list logo
