>> Such messages correspond to specific data structures.
>> * The log origin and log level are repeated there while the recorded
>> information might occasionally not be detailed enough.
>> I find that such details can be better handled by the software build
>> system.
…
> I appreciate you wan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Wed, 29 Jul 2015 21:17:18 +0200
Michał Zegan пишет:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
>
> I am trying to use systemd to run wildfly application server. It is
> being run by a shell script that runs a java vm in a separa
On 23 July 2015 at 23:17, Anne Mulhern wrote:
> Hi!
>
> We all know that using the journald native API it is possible to enrich the
> log
> entry data w/ key/value pairs, although this facility is Linux only.
> The set of key/value pairs which a message may log to the journal can
> constitute an
On 29 July 2015 at 20:02, Anne Mulhern wrote:
>
>
>
>
> - Original Message -
>> From: "Lennart Poettering"
>> To: "Anne Mulhern"
>> Cc: systemd-devel@lists.freedesktop.org
>> Sent: Thursday, July 23, 2015 9:21:44 AM
>> Subject: Re: [systemd-devel] Looking for experiences formalizing an A
Hi Markus,
On Wed, Jul 29, 2015 at 8:54 PM, SF Markus Elfring
wrote:
> Programs from the systemd software library output also some log messages
> as it is usual for such server applications.
>
> Such messages correspond to specific data structures.
> * The log origin and log level are repeated th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I am trying to use systemd to run wildfly application server. It is
being run by a shell script that runs a java vm in a separate process.
So, killing the script does not kill the other process.
The service is a simple type service, and I am wo
- Original Message -
> From: "Lennart Poettering"
> To: "Anne Mulhern"
> Cc: systemd-devel@lists.freedesktop.org
> Sent: Thursday, July 23, 2015 9:21:44 AM
> Subject: Re: [systemd-devel] Looking for experiences formalizing an API for
> journal messages
>
> On Thu, 23.07.15 09:17, An
Hello,
Programs from the systemd software library output also some log messages
as it is usual for such server applications.
Such messages correspond to specific data structures.
* The log origin and log level are repeated there while the recorded
information might occasionally not be detailed
On Wed, Jul 29, 2015 at 2:23 PM, Michael Biebl wrote:
> 2015-07-29 5:40 GMT+02:00 Tom Gundersen :
>> On Wed, Jul 29, 2015 at 1:21 AM, Michael Biebl wrote:
>>> something I was wondering regarding kdbus and udev.
>>> If udev wants to drop the netlink transport and instead rely on kdbus,
>>> would t
Heya!
The first systemd conference, systemd.conf, will take place on
November 5th-7th, 2015 at betahaus in Berlin-Kreuzberg, Germany. The
systemd project is one of the core components of most of today’s Linux
distributions. At systemd.conf 2015 we will discuss the state and
future of the Linux cor
Hi
Here's the next version of systemd, v223:
https://github.com/systemd/systemd/archive/v223.tar.gz
Many bug-fixes, code cleanups and some new additions to networkd and
resolved. As announced with the previous release, systemd-python has
been removed from upstream and now resides in its own
29.07.2015 14:40, SF Markus Elfring пишет:
This is *very* strange. The 'format' parameter should not contain that
"%s:%s:%d" prefix at all, as this cannot work of course because the
argument list doesn't match.
I guess that I wonder also about one of my own programming mistakes here.
Which
2015-07-29 5:40 GMT+02:00 Tom Gundersen :
> On Wed, Jul 29, 2015 at 1:21 AM, Michael Biebl wrote:
>> something I was wondering regarding kdbus and udev.
>> If udev wants to drop the netlink transport and instead rely on kdbus,
>> would this mean, systemd becomes mandatory in the initramfs to setup
On 07/29/2015 01:40 PM, SF Markus Elfring wrote:
>> Do you have *any* local modifications in your tree?
>
> Yes. - It seems that I was bitten by a format string mismatch during
> an attempt to display a few more implementation details for my needs.
>
>
> diff --git a/src/libsystemd/sd-device/dev
> This is *very* strange. The 'format' parameter should not contain that
> "%s:%s:%d" prefix at all, as this cannot work of course because the
> argument list doesn't match.
I guess that I wonder also about one of my own programming mistakes here.
> Which version of systemd are you based on?
la
On 07/29/2015 10:06 AM, SF Markus Elfring wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x76fefc78 in vfprintf () from /lib64/libc.so.6
> (gdb) bt full
> #0 0x76fefc78 in vfprintf () from /lib64/libc.so.6
> No symbol table info available.
> #1 0x77016f39
Hi,
Fedora and RHEL both ship initial-setup services. If initial-setup is
enabled then it must start *before* login is allowed.
Consider system which has multiple serial consoles attached then to
achieve above initial-setup-text.service must have
Before=serial-getty@ttyS0.service serial-gett
> This should usually generate a coredump.
I have regenerated the current software on my test system.
last commit: 6ad6d61f9ddd58983b075e4fbece30bae46fac37
Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service
systemd-udevd-kernel.socket systemd-udevd-control.socket &&
18 matches
Mail list logo
