On Sat, Dec 3, 2011 at 10:31 PM, Holger Winkelmann wrote:
> Hi all,
>
> We are about to renovate our embedded toolchain a bit and consider to
> integrate
> systemd as init. We are a bit concerned about the DBUS dependency in systemd
> as
> we have to meet a 4-8 MB hard disk (flash) requirement,
Hi all,
We are about to renovate our embedded toolchain a bit and consider to integrate
systemd as init. We are a bit concerned about the DBUS dependency in systemd as
we have to meet a 4-8 MB hard disk (flash) requirement,
I read about some other folks have used systems for embedded devices, but
I have digested our discussion now. Two questions came up:
The first one is a bit direct and blunt, my apologies for that. But I
want to make sure I put effort into the right place. Do you see any
benefit in an interface like I described (reading and writing the
journal from the syslogd)? Or do yo
On Sat, Dec 3, 2011 at 6:12 PM, Kay Sievers wrote:
> It's called a 'cursor', a text string that is portable even across
> machines, it will point to the closest possible record in the stream.
> In the idea it's like the git commit hash that identifies a commit, in
> the journal context it's just n
On Sat, Dec 3, 2011 at 17:36, Rainer Gerhards wrote:
> On Sat, Dec 3, 2011 at 5:18 PM, Kay Sievers wrote:
> One more question on the integration part. We now know that rsyslog
> needs to read the journal and convert that into proper syslog format.
> Given my experience with the Windows Event Log
On Sat, Dec 3, 2011 at 5:18 PM, Kay Sievers wrote:
> You can just add a tiny bridge or make rsyslog receive the proper data
> which has no fixed wire format at all, but is an API we can extend as
> needed.
>
> Honestly, I really don't understand your claims, all will be available
> to you with jus
On Sat, Dec 3, 2011 at 15:23, Rainer Gerhards wrote:
> On Sat, Dec 3, 2011 at 12:54 PM, Kay Sievers wrote:
>> Well, that's not making it hard to access information, it's trying
>> hard not to break established interfaces. If syslog *could* be
>> extended in a reasonable way, we wouldn't need a jo
On Sat, Dec 03, 2011 at 02:32:19PM +0100, Thomas Meyer wrote:
> Hi,
>
> I put a "user" unit in "/usr/lib/systemd/user" called
> "smServer.service":
>
> [Unit]
> Description=ShortMessage Server
> After=network.target
>
> [Service]
> Type=simple
> StandardOutput=syslog
> Environment=CLASSPATH=/usr
On Sat, Dec 3, 2011 at 12:54 PM, Kay Sievers wrote:
> Well, that's not making it hard to access information, it's trying
> hard not to break established interfaces. If syslog *could* be
> extended in a reasonable way, we wouldn't need a journal interface at
> all. Adding any information might brea
Hi,
I put a "user" unit in "/usr/lib/systemd/user" called
"smServer.service":
[Unit]
Description=ShortMessage Server
After=network.target
[Service]
Type=simple
StandardOutput=syslog
Environment=CLASSPATH=/usr/share/java/smServer.jar
WorkingDirectory=/home/thomas
ExecStart=/usr/bin/java smServer.
On Fri, Dec 2, 2011 at 21:21, Rainer Gerhards wrote:
> 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
11 matches
Mail list logo
