It won't help if the main process is still there and there is no new
process to kill.
---
Hi,
The second SIGTERM/SIGKILL is to kill ExecStopPost= if necessary, right? In
that case, this is a better solution.
Michael
src/core/service.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Hi,
Same thing with isolating a target. Job statuses are not printed out on the
console and it would be great to see what is being stopped/started at which
order for debugging.
Thanks.
On Wed, Jun 12, 2013 at 5:02 AM, Andrey Borzenkov wrote:
> В Wed, 12 Jun 2013 01:32:37 +0200
> Michael Olbric
On Tue, Jun 11, 2013 at 10:59 PM, Michael Olbrich
wrote:
> Not for me. "systemctl {start,stop} " never prints anything.
I think it "prints status" in the Unix way: stderr explanation on
failure and nothing on success.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
___
Hi,
On Wed, Jun 12, 2013 at 07:02:34AM +0400, Andrey Borzenkov wrote:
> В Wed, 12 Jun 2013 01:32:37 +0200
> Michael Olbrich пишет:
>
> > Hi,
> >
> > When booting or during shutdown systemd prints the start stop messages for
> > the services. Is it possible to get those messages when activating
On Tue, Jun 11, 2013 at 06:26:03PM +0200, Jason St. John wrote:
> From: "Jason St. John"
>
> "Corporation" was misspelled as "Coproration"
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/
When journald encounters a message with OBJECT_PID= set
coming from a priviledged process (UID==0), additional fields
will be added to the message:
OBJECT_UID=,
OBJECT_GID=,
OBJECT_COMM=,
OBJECT_EXE=,
OBJECT_CMDLINE=,
OBJECT_AUDIT_SESSION=,
OBJECT_AUDIT_LOGINUID=,
OBJECT_SYSTEMD_CGROUP=,
OBJECT_SY
В Wed, 12 Jun 2013 01:32:37 +0200
Michael Olbrich пишет:
> Hi,
>
> When booting or during shutdown systemd prints the start stop messages for
> the services. Is it possible to get those messages when activating a target
> with systemctl?
>
systemctl already prints status of job unless called w
Hi,
When booting or during shutdown systemd prints the start stop messages for
the services. Is it possible to get those messages when activating a target
with systemctl?
Regards,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions
If ExecStopPost= is defined then it is executed after SIGKILL. Otherwise
another round of SIGTERM/SIGSTOP is started which is rather useless when
the watchdog timeout hits.
So go directly to the final SIGKILL if ExecStopPost= is not defined.
---
Hi,
I did some more testing with this. I think this
I have a few Plugable multiseat consoles on Fedora 18. They mostly
work, but it seems after a day of use and logging out, the gdm greeter
never returns. Instead the monitor DPMS off and the Plugable
consoles have to be power cycled to get the greeter to return.
While the consoles are in this 'n
On Tue, 2013-06-11 at 17:14 -0400, Colin Walters wrote:
> The question I had looking at this is: what determines the ordering? I
> guess it's intended to be the version field, but what if I have both
> Debian and Fedora installed, the default comes down to whichever has a
> newer kernel?
Ah I'm
El 11/06/13 02:14, Kay Sievers escribió:
That's right, it does not pull-in selinux and as-needed can still get rid of it.
Yes, what is happening here, is that the linker used by the OP does not
default to "-Wl,--no-add-needed" (notice different from --as-needed, and
currently called --no-cop
On Tue, 2013-06-04 at 15:30 +0200, Lennart Poettering wrote:
> On Mon, 03.06.13 19:10, Colin Walters (walt...@verbum.org) wrote:
>
> > What's the implementation status of
> > http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ ?
> >
> > For example, do any patches exist for grub or sys
---
src/analyze/systemd-analyze.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
Nb: it might be even better to show the critical chain of a fictive
unit that would depend on everything in argv, but that's more
complicated to implement.
diff --git a/src/analyze/systemd
From: "Jason St. John"
"Corporation" was misspelled as "Coproration"
---
In case it matters, I am not employed by or affiliated with Intel.
src/bootchart/bootchart.c | 2 +-
src/bootchart/bootchart.h | 2 +-
src/bootchart/store.c | 2 +-
src/bootchart/store.h | 2 +-
src/bootchart/svg.
On Monday, June 10, 2013, Kay Sievers wrote:
> On Fri, Jun 7, 2013 at 11:46 PM, Sean McGovern wrote:
>> This is definitely not a common case as almost all of the other Linux
machines I have access to expose a network controller in domain 0.
>
> Yeah, I've only seen domains used on huge SGI machin
On Tue, Jun 11, 2013 at 10:59:42AM +0200, Thomas Bächler wrote:
> Am 11.06.2013 10:34, schrieb Colin Guthrie:
> > Without reading the code etc., I'm running systemd with that commit
> > (v204) and I don't get any conflicts for my -.mount unit...
> >
> > So it seems that code is not run for me for
On Tue, Jun 11, 2013 at 10:59 AM, Thomas Bächler wrote:
> I think this code is only called when there is no -.mount unit, which
> results from a missing entry for / in fstab. It is entirely possible
> that Ross didn't add / to his fstab by accident or on purpose.
I just want to point out: This is
Am 11.06.2013 10:34, schrieb Colin Guthrie:
> Without reading the code etc., I'm running systemd with that commit
> (v204) and I don't get any conflicts for my -.mount unit...
>
> So it seems that code is not run for me for whatever reason.
>
> After a very quick glance at the code, it could just
On Tue, Jun 11, 2013 at 10:07 AM, Umut Tezduyar wrote:
> Those 2 lines were added on 89b1d5e0e49d3b3501e5f3aadcad712290bcd9bf and the
> commit log explains why we needed them. "/" can be treated as special case
> and excluded.
If so, I guess also /usr and anything marked x-initrd.mount should be
'Twas brillig, and Ross Lagerwall at 11/06/13 08:19 did gyre and gimble:
> On Mon, Jun 10, 2013 at 08:30:40PM +0200, Lennart Poettering wrote:
>> Hmm, this is certainly weird. normally -.mount should not have any such
>> conflicts. I really wonder where you got those from... What is the
>> contents
Hi,
Those 2 lines were added on 89b1d5e0e49d3b3501e5f3aadcad712290bcd9bf and
the commit log explains why we needed them. "/" can be treated as special
case and excluded.
Thanks.
On Tue, Jun 11, 2013 at 9:19 AM, Ross Lagerwall wrote:
> On Mon, Jun 10, 2013 at 08:30:40PM +0200, Lennart Poetterin
On Mon, Jun 10, 2013 at 08:30:40PM +0200, Lennart Poettering wrote:
> Hmm, this is certainly weird. normally -.mount should not have any such
> conflicts. I really wonder where you got those from... What is the
> contents of /run/systemd/generator/-.mount for you?
>
AFAICT, mount_load_proc_self_m
23 matches
Mail list logo
