David Herrmann writes:
> Hi
>
> On Fri, Sep 12, 2014 at 11:21 AM, Jan Synacek wrote:
>> The prefix is always tested against normalized property names.
>> ---
>> src/sysctl/sysctl.c | 6 --
>> 1 file changed, 6 deletions(-)
>>
>> diff --git a/src/sysctl/sysctl.c b/src/sysctl/sysctl.c
>> index
Hi
On Mon, Sep 15, 2014 at 10:00 AM, Jan Synacek wrote:
> David Herrmann writes:
>> Nevertheless, the documentation should clearly state which input is
>> expected and the current code is definitely wrong as it only performs
>> one way conversions.
>
> Could you please point me to the right docu
We're currently running systemd-212. man doesn't seem to cover this.
--bind=, --bind-ro=
Bind mount a file or directory from the host into the
container. Either takes a path argument -- in which case the specified
path will be mounted from the host to the same path in the cont
David Herrmann writes:
> Hi
>
> On Mon, Sep 15, 2014 at 10:00 AM, Jan Synacek wrote:
>> David Herrmann writes:
>>> Nevertheless, the documentation should clearly state which input is
>>> expected and the current code is definitely wrong as it only performs
>>> one way conversions.
>>
>> Could yo
Hi
On Mon, Sep 15, 2014 at 11:26 AM, Jan Synacek wrote:
> David Herrmann writes:
>> Hi
>>
>> On Mon, Sep 15, 2014 at 10:00 AM, Jan Synacek wrote:
>>> David Herrmann writes:
Nevertheless, the documentation should clearly state which input is
expected and the current code is definitely
> After=syslog.target is redundant since a long time. Consider removing
> this. And After=network.target usually doesn't do what one might thing
> it does and with well written software that listens to rtnl or uses
> IP_FREEBIND not even necessary...
OK. I will remove the syslog. But I will have t
anybody an idea why?
Sep 15 13:14:43 localhost systemd-journal[4650]: Forwarding to syslog missed 2
messages.
Sep 15 13:15:13 localhost systemd-journal[4650]: Forwarding to syslog missed
196 messages.
Sep 15 13:15:44 localhost systemd-journal[4650]: Forwarding to syslog missed
236 messages.
Sep
David Herrmann writes:
> Hi
>
> On Mon, Sep 15, 2014 at 11:26 AM, Jan Synacek wrote:
>> David Herrmann writes:
>>> Hi
>>>
>>> On Mon, Sep 15, 2014 at 10:00 AM, Jan Synacek wrote:
David Herrmann writes:
> Nevertheless, the documentation should clearly state which input is
> expecte
Hi
On Mon, Sep 15, 2014 at 1:22 PM, Jan Synacek wrote:
> David Herrmann writes:
>> A path isn't necessarily a file-system path. With sysctl, we have to
>> ways to specify entries:
>>
>> 1) You can specify them via legacy sysctl(2) names. These names use
>> dots as separators
>>
>> 2) You can
Hi
On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald wrote:
> anybody an idea why?
The syslog daemon couldn't keep up with reading the log-messages. You
might wanna increase the syslog receive-queue in your syslog daemon or
make sure you don't flush that many messages to it.
Thanks
David
_
Am 15.09.2014 um 13:38 schrieb David Herrmann:
> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald wrote:
>> anybody an idea why?
>
> The syslog daemon couldn't keep up with reading the log-messages. You
> might wanna increase the syslog receive-queue in your syslog daemon or
> make sure you don't
Hi all
I currently manage several virtual machines which are not using systemd
because it's not default yet.
I've set them up to remote log to a RSyslog central point.
But, the future releases of my favorite distribution are going the
systemd way.
I must keep them logging to a central logg
Am 15.09.2014 um 13:47 schrieb Mihamina Rakotomandimby:
> I currently manage several virtual machines which are not using systemd
> because it's not default yet.
> I've set them up to remote log to a RSyslog central point.
> But, the future releases of my favorite distribution are going the syst
On Mon, Sep 15, 2014 at 02:47:12PM +0300, Mihamina Rakotomandimby wrote:
> Hi all
>
> I currently manage several virtual machines which are not using systemd
> because it's not default yet.
>
> I've set them up to remote log to a RSyslog central point.
>
> But, the future releases of my favorite
David Herrmann writes:
> Hi
>
> On Mon, Sep 15, 2014 at 1:22 PM, Jan Synacek wrote:
>> David Herrmann writes:
>>> A path isn't necessarily a file-system path. With sysctl, we have to
>>> ways to specify entries:
>>>
>>> 1) You can specify them via legacy sysctl(2) names. These names use
>>> do
On Sat, 13 Sep 2014 15:29:23 +0200
"Robert Milasan" wrote:
> Hello, I've found a lingering bug in udev since udev changed it's
> database name from long names to short names 'ex: b9:1'.
>
> The bug is more visible or reproducible on s390(x) has there, we can
> remove and add dasd disk/partitions
Hi
On Mon, Sep 15, 2014 at 1:43 PM, Reindl Harald wrote:
>
>
> Am 15.09.2014 um 13:38 schrieb David Herrmann:
>> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald
>> wrote:
>>> anybody an idea why?
>>
>> The syslog daemon couldn't keep up with reading the log-messages. You
>> might wanna increase
Am 15.09.2014 um 14:05 schrieb David Herrmann:
> On Mon, Sep 15, 2014 at 1:43 PM, Reindl Harald wrote:
>>
>> Am 15.09.2014 um 13:38 schrieb David Herrmann:
>>> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald
>>> wrote:
anybody an idea why?
>>>
>>> The syslog daemon couldn't keep up with rea
On Mon, Sep 15, 2014 at 1:38 PM, David Herrmann wrote:
> Hi
>
> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald wrote:
>> anybody an idea why?
>
> The syslog daemon couldn't keep up with reading the log-messages. You
> might wanna increase the syslog receive-queue in your syslog daemon or
> make s
Am 15.09.2014 um 14:10 schrieb Reindl Harald:
>
> Am 15.09.2014 um 14:05 schrieb David Herrmann:
>> On Mon, Sep 15, 2014 at 1:43 PM, Reindl Harald
>> wrote:
>>>
>>> Am 15.09.2014 um 13:38 schrieb David Herrmann:
On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald
wrote:
> anybody an
Am 15.09.2014 um 14:23 schrieb Umut Tezduyar Lindskog:
> On Mon, Sep 15, 2014 at 1:38 PM, David Herrmann wrote:
>> Hi
>>
>> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald
>> wrote:
>>> anybody an idea why?
>>
>> The syslog daemon couldn't keep up with reading the log-messages. You
>> might wan
On 12/09/14 16:03, Kay Sievers wrote:
> On Fri, Sep 12, 2014 at 3:04 PM, John Haxby wrote:
>> On 02/09/14 16:42, Kay Sievers wrote:
> Either the kernel has to provide a mechanism for the userspace to
> control onlining, or do it itself and provide a mechanism to prevent
> automatic onl
On Mon, Sep 15, 2014 at 2:34 PM, Reindl Harald wrote:
>
>
> Am 15.09.2014 um 14:23 schrieb Umut Tezduyar Lindskog:
>> On Mon, Sep 15, 2014 at 1:38 PM, David Herrmann
>> wrote:
>>> Hi
>>>
>>> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald
>>> wrote:
anybody an idea why?
>>>
>>> The syslog
Am 15.09.2014 um 15:19 schrieb Umut Tezduyar Lindskog:
> On Mon, Sep 15, 2014 at 2:34 PM, Reindl Harald wrote:
>>
>>
>> Am 15.09.2014 um 14:23 schrieb Umut Tezduyar Lindskog:
>>> On Mon, Sep 15, 2014 at 1:38 PM, David Herrmann
>>> wrote:
Hi
On Mon, Sep 15, 2014 at 1:20 PM, Reind
These are the only two places where this glibc-specific
header is included. However none of the definitions in it
seem to be used, so just remove the includes.
---
src/notify/notify.c | 1 -
src/path/path.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/notify/notify.c b/src/notify/n
---
src/shared/pty.c | 8
src/shared/pty.h | 1 -
2 files changed, 9 deletions(-)
diff --git a/src/shared/pty.c b/src/shared/pty.c
index 2863da4..a3332dd 100644
--- a/src/shared/pty.c
+++ b/src/shared/pty.c
@@ -541,14 +541,6 @@ int pty_write(Pty *pty, const void *buf, size_t size) {
Jan Včelák wrote on 15/09/14 12:03:
>>> > > 3.) In case of multiple instances, is there a way to control them all at
>>> > > once?
>>> > >
>> >
>> > Use PartOf= for this...
> OK. Thanks. I will take a look at it!
Just for a few more hints here:
You would create a knot.target unit which is just
Hi
On Mon, Sep 15, 2014 at 3:19 PM, John Haxby wrote:
> On 12/09/14 16:03, Kay Sievers wrote:
>> On Fri, Sep 12, 2014 at 3:04 PM, John Haxby wrote:
>>> When I think of changing the
>>> behaviour of any removable hardware, udev is automatically where I look
>>> first. So if I'm missing something
On 15/09/14 15:02, David Herrmann wrote:
> Hi
>
> On Mon, Sep 15, 2014 at 3:19 PM, John Haxby wrote:
>> On 12/09/14 16:03, Kay Sievers wrote:
>>> On Fri, Sep 12, 2014 at 3:04 PM, John Haxby wrote:
When I think of changing the
behaviour of any removable hardware, udev is automatically w
Hi
On Mon, Sep 15, 2014 at 4:22 PM, John Haxby wrote:
> I really appreciate proper explanations, thank you.
Quite simple: We want to avoid calling into udev and back into the
kernel if we there's a way to skip this step. That is, the default
should work without udev.
Reasons:
* We want init=/b
Hi
On Mon, Sep 15, 2014 at 3:29 PM, Emil Renner Berthing wrote:
> ---
> src/shared/pty.c | 8
> src/shared/pty.h | 1 -
> 2 files changed, 9 deletions(-)
>
> diff --git a/src/shared/pty.c b/src/shared/pty.c
> index 2863da4..a3332dd 100644
> --- a/src/shared/pty.c
> +++ b/src/shared/pty.
Hi
On Mon, Sep 15, 2014 at 3:29 PM, Emil Renner Berthing wrote:
> These are the only two places where this glibc-specific
> header is included. However none of the definitions in it
> seem to be used, so just remove the includes.
Looks good. I think we used error() in the past, but that's long g
Hi,
On 15 September 2014 16:59, David Herrmann wrote:
> Hi
>
> On Mon, Sep 15, 2014 at 3:29 PM, Emil Renner Berthing
> wrote:
>> ---
>> src/shared/pty.c | 8
>> src/shared/pty.h | 1 -
>> 2 files changed, 9 deletions(-)
>>
>> diff --git a/src/shared/pty.c b/src/shared/pty.c
>> index 2
Is there a way to inhibit the systemd automatic activation of swap on GPT disks
that use the linux swap partition type GUID? The desire to do this has come up
in these two bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1141700
clone of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=11
On 09/15/2014 04:30 PM, Chris Murphy wrote:
The issue is when booting live media (e.g. for OS installs), the autoactivation
is causing some installer confusion.
Should be fixed downstream in Anaconda/Live script.
___
systemd-devel mailing list
syste
> From: Andrei Borzenkov
> At least, it is impossible to achieve what the goal of OP was -
> attempt to automount device exactly once on system boot and give up if
> it was not successful. Which had been semantic of /etc/fstab for quite
> some time.
I don't have a need to "automount device exact
I made an incorrect diagnosis. systemd-gpt-auto-generator is not
auto-activating this GPT swap partition. It's actually the live media's init
script in the initramfs.
When I use 'noswap' boot parameter the swap isn't activated; I assume systemd
doesn't look for 'noswap'. So the behavior I'm see
This sentence can be misread to mean that "\x20" is the escape code for
"-" which is the only character explicitly mentioned. This lead to at
least one user loosing hair over why a mount unit for "/foo/bar-baz"
didn't work. The example escape is arbitrary so lets prevent hair loss.
---
man/systemd
From: Thomas Hindoe Paaboel Andersen
sd_bus_message_get_errno can currently return either a number of
different poitive errno values (from bus-error-mapping), or a negative
EINVAL if passed null as parameter.
The check for null parameter was introduced in
40ca29a1370379d43e44c0ed425eecc7218dcbc
From: Thomas Hindoe Paaboel Andersen
The 3 calls to sd_bus_error_get_errno appear to expect a negative
return value.
This patch negates the returned value so it matches the other error
cases in the 3 functions where sd_bus_error_get_errno is used.
---
src/libsystemd-terminal/sysview.c | 6 +++--
Hi,
I wrote a small patch for user-mode linux to register with machined by
calling "CreateMachine". Is this a good idea to do so?
I think machined gives you a nice overview over all running UML
instances, also you get the scope unit and the control groups with above
registration to machined. anyt
Hi Alban,
Sorry for the long delay on this.
On 08/14/2014 01:21 PM, Alban Crequy wrote:
> Before Linux commit 25888e (from 2.6.37-rc4, Nov 2010), fd-passing on Unix
> sockets could recursively be stacked, allowing a process to exhaust the open
> files limit (/proc/sys/fs/file-max) on the system w
On Wed, Sep 10, 2014 at 11:20 AM, wrote:
> From: Philippe De Swert
>
> Hi,
>
> Yesterday I finally got to revive the systemd Coverity project on
> scan.coverity.org Unfortunately to see the errors reported you need
> to sign up, but I will make sure to approve requests for seeing the
> "bugs" wh
43 matches
Mail list logo
