On Thu, Jan 24, 2013 at 6:07 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Thu, Jan 24, 2013 at 04:59:00PM -0800, Khem Raj wrote:
>> On Thu, Jan 24, 2013 at 1:42 PM, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> >
>> > libsystemd-core is linked with libsystemd-daemon on its own.
>> > Thus this patch sho
On Thu, 24.01.13 17:47, Colin Walters ([email protected]) wrote:
> I don't see why this should be logged at all, so let's delete it.
Applied. I also removed a couple of other messages that appear a bit too
much to me.
Lennart
--
Lennart Poettering - Red Hat, Inc.
_
On Thu, Jan 24, 2013 at 04:59:00PM -0800, Khem Raj wrote:
> On Thu, Jan 24, 2013 at 1:42 PM, Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > libsystemd-core is linked with libsystemd-daemon on its own.
> > Thus this patch shouldn't be necessary. Are you observing
> > some actual build brackage? If so
I think mounting the journal directory over NFS is a bad idea. It's
most of why we've worked on journal2gelf at Pantheon and supported the
gateway HTTP-based access work.
On Thu, Jan 24, 2013 at 8:23 AM, Cliff Brake wrote:
> Hello,
>
> We have:
>
> * systemd v187 on 8 ARM systems
> * all 8 system
On Wed, Jan 23, 2013 at 09:28:23AM +0100, Umut Tezduyar wrote:
> Regardless of this patch, it might be a good idea to mention
> /proc/self/mountinfo in systemd.mount(5) as currently there is no mention
> of .mount files might pop up by systemd by looking at /proc/self/mountinfo.
> Thanks
Done.
Zby
On Thu, Jan 24, 2013 at 1:42 PM, Zbigniew Jędrzejewski-Szmek
wrote:
>
> libsystemd-core is linked with libsystemd-daemon on its own.
> Thus this patch shouldn't be necessary. Are you observing
> some actual build brackage? If so, what arch?
I am seeing it on ppc. while I do see the relevant .la f
On Wed, Jan 23, 2013 at 09:23:49AM +0100, Umut Tezduyar wrote:
> ---
> src/core/mount.c |6 +-
> 1 files changed, 5 insertions(+), 1 deletions(-)
Applied.
Zbyszek
___
systemd-devel mailing list
[email protected]
http://lists.fr
On Wed, Jan 23, 2013 at 02:12:16PM +0100, Michael Olbrich wrote:
> For services without ExecStop= the state SERVICE_STOP is never
> entered. as a result the watchdog timer is not stopped and the service
> is restarted (if it is configuered to restart). Stopping the watchdog
> timer for SERVICE_STO
On Thu, Jan 24, 2013 at 06:06:00PM +0100, Frederic Crozat wrote:
> Hi all,
>
> while working on another bug, I discovered the "strange" way systemd is
> parsing Environment= in .service and thought it was worth documenting
> (because I don't expect people to find this syntax by themselves unless
Lennart,
There's more to it than that. The DECnet kernel module must first be loaded so
that it creates /proc/net/decnet*. When the dnetd service is started, it
parses /etc/decnet.conf and writes the DECnet host address to
/proc/sys/net/decnet/node_address and the default DECnet device (inter
On Thu, 24.01.13 14:08, Larry Baker ([email protected]) wrote:
> I am converting the init script (see below) for Linux DECnet
> (http://sourceforge.net/projects/linux-decnet). This is my first exposure to
> systemd. Naturally, my first try failed. So, now I am taking baby steps.
>
> The Linux D
On Thu, 24.01.13 00:29, Lars Kellogg-Stedman ([email protected]) wrote:
Heya,
Currently, our idea of containers is that no devices beyond /dev/null,
/dev/zero, /dev/random and friends are available to them, and if you
have any others you want to expose they need to be managed by the
container manag
2013/1/24 Larry Baker :
>...
> Then it looks for evidence that the decnet kernel module is loaded by
> testing for the file /proc/net/decnet. If necessary, it loads the decnet
> kernel module and checks again for /proc/net/decnet. I have already built
> the decnet kernel module and I can load it
I don't see why this should be logged at all, so let's delete it.
Signed-off-by: Colin Walters
---
src/core/selinux-access.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
>From c79f1c8f0f6bc6f56c132983fd91292176bcfbdc Mon Sep 17 00:00:00 2001
From: Colin Walters
Date: Thu, 24 Ja
I am converting the init script (see below) for Linux DECnet
(http://sourceforge.net/projects/linux-decnet). This is my first exposure to
systemd. Naturally, my first try failed. So, now I am taking baby steps.
The Linux DECnet init script can start either or both the dnetd or phoned
daemons
On Tue, Jan 22, 2013 at 02:07:10PM -0800, David Strauss wrote:
> A quick web search is failing me, so I'll ask here: is this "type X" a
> novel thing you're introducing or something used elsewhere? I don't
> see it mentioned in Lennart's overview of tmp storage areas [1],
> either.
Yeah, this seems
On Tue, Jan 22, 2013 at 06:32:49PM -0800, Khem Raj wrote:
> test-unit-file links with libsystemd-core which needs
> sd_* symbols from libsystemd-daemon
Hi,
libsystemd-core is linked with libsystemd-daemon on its own.
Thus this patch shouldn't be necessary. Are you observing
some actual build bracka
Hi all,
while working on another bug, I discovered the "strange" way systemd is
parsing Environment= in .service and thought it was worth documenting
(because I don't expect people to find this syntax by themselves unless
they read the parsing code ;)
--
Frederic Crozat
SUSE
>From 2cfd1ed4d853
Hello,
We have:
* systemd v187 on 8 ARM systems
* all 8 systems mount the /var/log/journal directory on a server via NFS
We like the idea that all journals can be located in one place and
querried on the server at the same time -- very neat. However, thus
far, it seems like it performs very bad
> That looks pretty different from the above output.
Yeah, that's weird. And after a restart, "udevadm info ..." actually shows:
P: /devices/virtual/net/eth0
E: DEVPATH=/devices/virtual/net/eth0
E: ID_NET_NAME_MAC=enx00163e05244e
E: ID_OUI_FROM_DATABASE=Xensource, Inc.
E: IFINDEX=39
E: INTERFACE
On Thu, Jan 24, 2013 at 3:18 PM, Lars Kellogg-Stedman wrote:
>> If udev runs in the container, maybe it should just made working.
>>
>> What does:
>> udevadm test /sys/class/net/eth0
>> say about TAGS=:systemd and such ...
>
> Running this:
>
> # udevadm test /sys/class/net/eth0 | grep -i syst
> If udev runs in the container, maybe it should just made working.
>
> What does:
> udevadm test /sys/class/net/eth0
> say about TAGS=:systemd and such ...
Running this:
# udevadm test /sys/class/net/eth0 | grep -i systemd
Yields:
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
On Thu, Jan 24, 2013 at 1:58 PM, Lars Kellogg-Stedman wrote:
>>> It is possible to
>>> synthesize these dependencies so that it is not necessary to modify
>>> distribution-maintained files?
>>
>> What do you mean?
>
> So, I have existing distribution scripts that include BindTo
> directives as des
>> It is possible to
>> synthesize these dependencies so that it is not necessary to modify
>> distribution-maintained files?
>
> What do you mean?
So, I have existing distribution scripts that include BindTo
directives as described earlier. If systemd-udevd is not generating
the correct notifica
On Thu, Jan 24, 2013 at 1:20 PM, Lars Kellogg-Stedman wrote:
>> Are you sure you see the process running there?
>
> I see systemd-udevd running:
>
> # systemd-detect-virt
> lxc-libvirt
> # ps -fe
> UIDPID PPID C STIME TTY TIME CMD
> root 1 0 0 Jan23 ?00:00:0
> Are you sure you see the process running there?
I see systemd-udevd running:
# systemd-detect-virt
lxc-libvirt
# ps -fe
UIDPID PPID C STIME TTY TIME CMD
root 1 0 0 Jan23 ?00:00:00 /sbin/init
root 8 1 0 Jan23 ?00:00:00 /usr/lib/systemd
On Thu, Jan 24, 2013 at 6:29 AM, Lars Kellogg-Stedman wrote:
> I am running Linux under LXC. I have a systemd unit file for dhcpcd (a
> DHCP client) that includes:
I
> understand that this may be a udev problem, and there are posts out
> there indicating that udev had problems running in a contain
On Thu, Jan 24, 2013 at 9:23 AM, Tomasz Torcz wrote:
> On Thu, Jan 24, 2013 at 12:29:41AM -0500, Lars Kellogg-Stedman wrote:
>> BindsTo=sys-subsystem-net-devices-eth0.device
>>
>> Systemd (197) does not appear to be aware of this interface, and
>> ultimately gives up with the following error:
>>
On Thu, Jan 24, 2013 at 12:29:41AM -0500, Lars Kellogg-Stedman wrote:
> BindsTo=sys-subsystem-net-devices-eth0.device
>
> Systemd (197) does not appear to be aware of this interface, and
> ultimately gives up with the following error:
>
> Timed out waiting for device sys-subsystem-net-devices
29 matches
Mail list logo
