On Fri, Dec 2, 2011 at 7:47 PM, Kay Sievers wrote:
>>> Well, if syslogd, or any other consumer, is interested in the
>>> metadata, it should not rely in /dev/log. /dev/log will probably stay
>>> what it is which is mostly plain old syslog with a header and a
>>> timestamp and the human readable st
On Fri, Dec 2, 2011 at 19:07, Rainer Gerhards wrote:
> On Fri, Dec 2, 2011 at 6:59 PM, Kay Sievers wrote:
>> On Fri, Dec 2, 2011 at 17:02, Rainer Gerhards wrote:
>> Well, if syslogd, or any other consumer, is interested in the
>> metadata, it should not rely in /dev/log. /dev/log will probably
Hi all,
I'm just learning to know systemd and it seems very nice, but I have
one question/consideration.
System V init scripts are self documenting and customizable: they are
scripts. It is easy to read and edit them. One can read through the
init process from step one and learn to know every ste
On Fri, Dec 2, 2011 at 6:59 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 17:02, Rainer Gerhards wrote:
>> On Fri, Dec 2, 2011 at 4:39 PM, Kay Sievers wrote:
>
>>> /dev/log will be read by journald. The syslog.socket filedescriptor
>>> that the syslog daemon receives, will be provided by journ
On Fri, Dec 2, 2011 at 17:02, Rainer Gerhards wrote:
> On Fri, Dec 2, 2011 at 4:39 PM, Kay Sievers wrote:
>> /dev/log will be read by journald. The syslog.socket filedescriptor
>> that the syslog daemon receives, will be provided by journald and have
>> all the messages which are received by /de
Remove spurious '}'. This error went unnoticed so far because Bash
doesn't complain.
Signed-off-by: Ramkumar Ramachandra
---
src/systemd-bash-completion.sh |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/systemd-bash-completion.sh b/src/systemd-bash-completion.sh
Adding support for ZSH requires two changes:
1. The syntax for initializing associative arrays are different in
Bash 4 and ZSH. However, array access has the same syntax in both- so
use explicit assignments.
2. Bash uses a different completion system, and the function
complete() is undefined in ZS
Teach the console, getty, and serial m4 scripts about Debian.
Signed-off-by: Ramkumar Ramachandra
---
units/console-shell.service.m4 |3 +++
units/[email protected]|3 +++
units/[email protected] |3 +++
3 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/un
Hi,
I've just started scratching the surface: lack of autocomplete in ZSH
is annoying. So, here are a couple of patches fixing that, along with
a better version of a patch I messed up earlier today [1].
Thanks for reading.
-- Ram
[1]: <[email protected]>
Ramk
On Fri, Dec 2, 2011 at 4:39 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 16:14, Rainer Gerhards wrote:
>> On Fri, Dec 2, 2011 at 2:49 PM, Kay Sievers wrote:
>>> On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
as you probably know, I am not a big fan of the journald proposal, but
>>
On Fri, Dec 2, 2011 at 16:14, Rainer Gerhards wrote:
> On Fri, Dec 2, 2011 at 2:49 PM, Kay Sievers wrote:
>> On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
>>> as you probably know, I am not a big fan of the journald proposal, but
>>> that's not the point of my question. I am thinking abou
On Fri, Dec 2, 2011 at 2:49 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
>> as you probably know, I am not a big fan of the journald proposal, but
>> that's not the point of my question. I am thinking about how to
>> integrate journal data into a syslog logging so
Hi Tollef,
Tollef Fog Heen wrote:
> | diff --git a/src/hostname-setup.c b/src/hostname-setup.c
> | index 2c2f10c..918525d 100644
> | --- a/src/hostname-setup.c
> | +++ b/src/hostname-setup.c
> | @@ -32,6 +32,8 @@
> [...]
> Not needed, the top of read_hostname from the same file.
and
> | diff --g
]] Ramkumar Ramachandra
| diff --git a/src/hostname-setup.c b/src/hostname-setup.c
| index 2c2f10c..918525d 100644
| --- a/src/hostname-setup.c
| +++ b/src/hostname-setup.c
| @@ -32,6 +32,8 @@
|
| #if defined(TARGET_FEDORA) || defined(TARGET_ALTLINUX) ||
defined(TARGET_MANDRIVA) || defined(TA
On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
> as you probably know, I am not a big fan of the journald proposal, but
> that's not the point of my question. I am thinking about how to
> integrate journal data into a syslog logging solution.
You know that the syslog daemon will still see e
Hi there,
as you probably know, I am not a big fan of the journald proposal, but
that's not the point of my question. I am thinking about how to
integrate journal data into a syslog logging solution. So I have a
couple of questions in regard to accessing the journal. The most
important one is how
Teach systemd about the location of the hostname, distribution version
file, and tweak the various m4 scripts in units/.
Signed-off-by: Ramkumar Ramachandra
---
Started using systemd on my Debian machine yesterday- here's a quick
patch for starters.
Thanks for reading.
[Please CC me on repli
Hey,
2011/12/1 Chen Jie :
> Hi,
>
> Thanks for the reply.
>
> 2011/11/30 Michal Schmidt :
>> On 11/30/2011 10:49 AM, Chen Jie wrote:
>>>
>>> (see the full syslog at
>>>
>>> http://lists.freedesktop.org/archives/dbus/attachments/2025/e9c204bb/attachment-0001.obj)
>>
>>
>> The kernel modules fai
18 matches
Mail list logo