-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Fri, 31 Jul 2015 00:19:06 +0200
Michał Zegan пишет:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
> What is the recommended easy way to start processes that stay longer
> like screen in case I want to do it by first executing su to
В Thu, 30 Jul 2015 16:53:43 -0500
Lesley Kimmel пишет:
> I can't really change anything about the way that the Node Manager does it's
> job. That all takes place outside of systemd. If I used the PIDFile option in
> the original systemd service (executing the WLST process), let's call this
> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
What is the recommended easy way to start processes that stay longer
like screen in case I want to do it by first executing su to change to
the target user?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBAgAGBQJVuqLXAAoJEHb1CzgxXKwY2Y4
I can't really change anything about the way that the Node Manager does it's
job. That all takes place outside of systemd. If I used the PIDFile option in
the original systemd service (executing the WLST process), let's call this
weblogic.service, and the PIDFile pointed to the PID file created
On Thu, Jul 30, 2015 at 9:40 PM, Lesley Kimmel
wrote:
> All;
>
> I'm struggling with figuring out how to migrate some SysVInit scripts to
> systemd. Specifically, this service launches WebLogic Managed Server (Java)
> instances Let me describe the process flow of my current service to you:
>
> -T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks, tracking it.
W dniu 2015-07-30 o 20:41, Andrei Borzenkov pisze:
> В Thu, 30 Jul 2015 20:07:03 +0200 Michał Zegan
> пишет:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>
>> Here is a log from appserver.service: appserver.service: Tryin
On Mon, Jul 27, 2015 at 1:26 PM, Lennart Poettering
wrote:
> On Thu, 16.07.15 12:40, Chris Murphy (li...@colorremedies.com) wrote:
>
>> Hence the question, rephrased, does systemd expect /var/lib/machines
>> to be an actual subvolume rather than a mountpoint backed by a mounted
>> subvolume?
>
>
On Thu, Jul 30, 2015 at 9:47 PM, Anne Mulhern wrote:
>
> Where can the support for structured logging be found in the kernel?
> It seems tricky, given the kernel's constraints, to support arbitrary
> structured logging.
>
It was added to kernel/printk.c in v3.5 – printk_emit() accepts an array of
- Original Message -
> From: "Zbigniew Jędrzejewski-Szmek"
> To: "Anne Mulhern"
> Cc: systemd-devel@lists.freedesktop.org
> Sent: Thursday, July 30, 2015 1:04:55 PM
> Subject: Re: [systemd-devel] in-kernel structured logging
>
> On Thu, Jul 30, 2015 at 12:16:03PM -0400, Anne Mulhern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Thu, 30 Jul 2015 20:07:03 +0200
Michał Zegan пишет:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Here is a log from appserver.service:
> appserver.service: Trying to enqueue job
> appserver.service/stop/replace
> appserver.service: Inst
All;
I'm struggling with figuring out how to migrate some SysVInit scripts to
systemd. Specifically, this service launches WebLogic Managed Server (Java)
instances Let me describe the process flow of my current service to you:
-The init service/script launches a Java process called WLST which e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Thu, 30 Jul 2015 19:57:42 +0200
Michał Zegan пишет:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> First, it seems that sighup is NOT sent by default.
Yes, sorry, my mistake.
> Second, setting SendSIGKILL to no fixes the problem (and that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a log from appserver.service:
appserver.service: Trying to enqueue job
appserver.service/stop/replace
appserver.service: Installed new job appserver.service/stop as 16578
appserver.service: Enqueued job appserver.service/stop as 16578
app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, it seems that sighup is NOT sent by default.
Second, setting SendSIGKILL to no fixes the problem (and that should
not be needed), that probably means the second process gets sigkill.
W dniu 2015-07-30 o 18:23, Andrei Borzenkov pisze:
> В Thu, 3
On Thu, Jul 30, 2015 at 12:16:03PM -0400, Anne Mulhern wrote:
> Hi!
>
> This is really closely related to my previous question re. formalizing an API.
>
> In the design document
> (https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUEHIX3MSTs)
> there is a statement about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Thu, 30 Jul 2015 14:51:44 +0200
Michał Zegan пишет:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Actually when I have sent the question I had systemd-222.
> now it is 223 and result is the same.
> Unit file is at http://webczatnet.pl/web
Hi!
This is really closely related to my previous question re. formalizing an API.
In the design document
(https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUEHIX3MSTs)
there is a statement about a future intention to support "in-kernel structured
logging".
Are things l
On Thu, Jul 30, 2015 at 10:56:42AM -0400, Anne Mulhern wrote:
> > On Wed, Jul 29, 2015 at 03:02:26PM -0400, Anne Mulhern wrote:
> > > What I'm wondering about is the existence of some processes (not systemd),
> > > that have an
> > > agreement on a set of key-value pairs that they communicate with
- Original Message -
> From: "Zbigniew Jędrzejewski-Szmek"
> To: "Anne Mulhern"
> Cc: systemd-devel@lists.freedesktop.org
> Sent: Thursday, July 30, 2015 10:01:54 AM
> Subject: Re: [systemd-devel] Looking for experiences formalizing an API for
> journal messages
>
> On Wed, Jul 29,
On 07/30/2015 03:53 PM, Umut Tezduyar Lindskog wrote:
> Fantastic! Tried to purchase a ticket but seems like PayPal is the
> only supported payment. Is this a glitch?
For now, only going with PayPal as checkout option was the easiest way
of get the sale going. If that turns out to be a major probl
On Wed, Jul 29, 2015 at 03:02:26PM -0400, Anne Mulhern wrote:
> What I'm wondering about is the existence of some processes (not systemd),
> that have an
> agreement on a set of key-value pairs that they communicate with through the
> journal.
There was work done on converting abrt to use the jo
Fantastic! Tried to purchase a ticket but seems like PayPal is the
only supported payment. Is this a glitch?
Umut
On Wed, Jul 29, 2015 at 5:55 PM, Lennart Poettering
wrote:
> Heya!
>
> The first systemd conference, systemd.conf, will take place on
> November 5th-7th, 2015 at betahaus in Berlin-K
On Wed, 29.07.15 15:02, Anne Mulhern (amulh...@redhat.com) wrote:
> > systemd of courses uses its on its own, and we tried to document
> > the fields we use in systemd.journal-fields(7), though it might be
> > slightly incomplete.
> >
> > But yes, this is indeed API, and deserves complete documen
On Thu, 30.07.15 08:16, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
> >> 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 suc
On Thu, Jul 30, 2015 at 4:20 PM, Sakhi Hadebe wrote:
>
> Jul 30 15:13:30 monitor.sanren.ac.za nagios[32281]: ***> One or more
> problems was encountered while processing the config files...
>
That sounds like a nagios problem?
--
Mantas Mikulėnas
___
Hi,
I have just installed the latest nagios mointoring server on debian 8.1
(jessie). When trying to restart the nagios service, it fails, see the
error below:
[] Starting nagios (via systemctl): nagios.serviceJob for
nagios.service failed. See 'systemctl status nagios.service' and
'journalc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually when I have sent the question I had systemd-222.
now it is 223 and result is the same.
Unit file is at http://webczatnet.pl/webczat/appserver.service
W dniu 2015-07-30 o 05:36, Andrei Borzenkov pisze:
> В Wed, 29 Jul 2015 21:17:18 +0200 Mich
>> I find that the change acceptance is unclear for fine-tuning of this software
>> also around message log programming interfaces.
>> Which design approaches do you find acceptable for further considerations?
>
> Sorry, I really can't follow.
How do you generally think about any further fine-tun
On Thu, Jul 30, 2015 at 8:16 AM, SF Markus Elfring
wrote:
>>> 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 han
29 matches
Mail list logo
