On Fri, Nov 09, 2012 at 12:45:22AM +, "Jóhann B. Guðmundsson" wrote:
> What's lacking is the status to be shown when units are manually
> started/reloaded/restart/stopped there is just one slight problem
> implementing that which is you dont want that output when the
> service is started at boo
On Fri, Nov 09, 2012 at 12:45:22AM +, "Jóhann B. Guðmundsson" wrote:
> Not the first and probably not the last that expected that behavior
> and proposed this.
>
> What's lacking is the status to be shown when units are manually
> started/reloaded/restart/stopped there is just one slight probl
On 11/09/2012 12:23 AM, William Giokas wrote:
All,
I have been using systemd for a few months now, and I must say, it is a
great init system. I myself am no coder, else I would attempt to write
something to do just this. One not-dealbreaking thing that I do find
lacking is a verbose option for `
All,
I have been using systemd for a few months now, and I must say, it is a
great init system. I myself am no coder, else I would attempt to write
something to do just this. One not-dealbreaking thing that I do find
lacking is a verbose option for `systemctl start `, essentially
running `journalc
On Thu, Nov 08, 2012 at 04:56:03PM -0500, Colin Walters wrote:
> Sorry about the tone in the last message, it was unnecessary. There's
> just some history here dating from the libxml2 days...
No worries, no offence taken :-)
> On Thu, 2012-11-08 at 17:38 +0100, Daniel P. Berrange wrote:
>
> > Y
Sorry about the tone in the last message, it was unnecessary. There's
just some history here dating from the libxml2 days...
On Thu, 2012-11-08 at 17:38 +0100, Daniel P. Berrange wrote:
> Yeah, we've looked at & borrowed code from GLib in a few cases
> now, notably threads and atomic ops. I've p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2012 01:18 PM, Douglas, William wrote:
> On Thu, Nov 8, 2012 at 8:54 AM, Kay Sievers wrote:
>> On Thu, Nov 8, 2012 at 8:31 AM, William Douglas
>> wrote:
>>> "Kok, Auke-jan H" writes:
I wrote a demo application that uses the jour
On Thu, Nov 8, 2012 at 8:54 AM, Kay Sievers wrote:
> On Thu, Nov 8, 2012 at 8:31 AM, William Douglas
> wrote:
>> "Kok, Auke-jan H" writes:
>>>
>>> I wrote a demo application that uses the journal API to scan for SSH
>>> bruteforce logs in the journal, called "tallow".
>>
>> Since Auke is on vaca
On Thu, Nov 8, 2012 at 8:31 AM, William Douglas
wrote:
> "Kok, Auke-jan H" writes:
>>
>> I wrote a demo application that uses the journal API to scan for SSH
>> bruteforce logs in the journal, called "tallow".
>
> Since Auke is on vacation now (and would *never* read email or work on
> projects o
On Thu, 2012-11-08 at 11:13 +0100, Robert Milasan wrote:
> From: Neil Brown
> Date: Thu, 8 Nov 2012 10:39:06 +0100
> Subject: [PATCH] If a 'change' event does not get handled by udev until
> after the device has subsequently disappeared, udev mis-handles
> it. This can happen with 'md' devices wh
On Thu, Nov 08, 2012 at 11:22:43AM -0500, Colin Walters wrote:
> On Thu, 2012-11-08 at 16:59 +0100, Daniel P. Berrange wrote:
>
> > The problem is that when libvirt does fork() to create client processes,
> > one of the things it does is to iterate from 0 -> sysconf(_SC_OPEN_MAX),
> > closing ever
On Thu, 2012-11-08 at 16:59 +0100, Daniel P. Berrange wrote:
> The problem is that when libvirt does fork() to create client processes,
> one of the things it does is to iterate from 0 -> sysconf(_SC_OPEN_MAX),
> closing every file descriptor, except those in its whitelist.
You could iterate over
I recently introduced support for libvirt logging to journald. Initially I
had intended to use libsystemd-journal.so for the logging, however, in the
end I made libvirt directly communicate with sendmsg().
First, I wanted to confirm two interface stability issues.
- Is the client app -> journald
From: Neil Brown
Date: Thu, 8 Nov 2012 10:39:06 +0100
Subject: [PATCH] If a 'change' event does not get handled by udev until
after the device has subsequently disappeared, udev mis-handles
it. This can happen with 'md' devices which emit a change
event and then a remove event when they are stop
14 matches
Mail list logo
