I'm getting these at startup:
systemd[1]: File /lib/systemd/system/systemd-journald.service:33
configures an IP firewall (IPAddressDeny=any), but the local system does
not support BPF/cgroup based firewalling.
systemd[1]: Proceeding WITHOUT firewalling in effect!
systemd[1]: File /lib/systemd/
On Fri, Oct 27, 2017 at 4:41 PM, Tom Matthews
wrote:
> Good afternoon,
> Is there a good reason why list-units pads the description field out with
> trailing whitespace ?
Probably so that the line would be fully underlined; see
https://github.com/systemd/systemd/pull/6601
--
Mantas Mikulėnas
Good afternoon,
Is there a good reason why list-units pads the description field out with
trailing whitespace ?
$ systemctl list-units | cat -vet | head -6
UNIT
LOAD ACTIVE SUB DESCRI
Am Dienstag, den 27.06.2017, 13:48 +0800 schrieb 清辰:
> for example: service nscd
> 1.execute: systemctl stop nscd.service
> stop nscd process actually
> 2.execute: /usr/bin/nscd
> start nscd by shell command
> 3.execute: systemctl status nscd.service
> inactive(dead)
> systemctl can't know
On 27/10/17 12:25, Lennart Poettering wrote:
> On Fr, 27.10.17 11:43, D.S. Ljungmark ([email protected]) wrote:
>
>> So, I've got a piece of hardware I want to do a final handover to just
>> around reboot.target / shutdown.target
>>
>> This will then cause the entire CPU and hardware allocated
okay, thank you for your help very much.
-- --
??: Lennart Poettering
: 2017??10??27?? 18:27
??: <[email protected]>
: Oliver Neukum , systemd-devel
: [systemd-devel] ?? ?? [systemd-de vel] sys temctl
ca
Am 27.10.2017 um 12:25 schrieb 清辰:
When executing 'service xxx restart', actually systemd will execute
'service xxx start', and then 'service xxx stop'.
But my restart action is different from stop action, can I customize my
'restart'?
no - fix the service
this sounds somehow as you have mu
Am 27.10.2017 um 11:53 schrieb 清辰:
Where is the 'service xxx status' result stored? Or can I change the
service status manually, when start / stop the service outside of systemd
just don't start it outside systemd - yes it's really that easy
___
sys
On Fr, 27.10.17 11:43, D.S. Ljungmark ([email protected]) wrote:
> So, I've got a piece of hardware I want to do a final handover to just
> around reboot.target / shutdown.target
>
> This will then cause the entire CPU and hardware allocated to it to
> actually drop power (and schedule re-power)
When executing 'service xxx restart', actually systemd will execute 'service
xxx start', and then 'service xxx stop'.
But my restart action is different from stop action, can I customize my
'restart'?
-- --
??: "Lennart Poettering";
: 2017
On Fr, 27.10.17 18:25, 清辰 ([email protected]) wrote:
> When executing 'service xxx restart', actually systemd will execute 'service
> xxx start', and then 'service xxx stop'.
> But my restart action is different from stop action, can I customize my
> 'restart'?
First of all, note that systemd do
see man:bootup for the general architecture of shutdown and
man:systemd-shutdown for how to add a script as the "ultimate phase" of
the shutdown
doing it with services is tricky, your approch will make it be called at
shutdown but you did not specify "when" during shutdown, so systemd
might s
On Fr, 27.10.17 17:53, 清辰 ([email protected]) wrote:
> Hi,
>
>
> Where is the 'service xxx status' result stored? Or can I change the
> service status manually, when start / stop the service outside of
> systemd.
PID 1 maintains a per-service record in its internal memory. Only
PID 1 itself has
Hi,
Where is the 'service xxx status' result stored? Or can I change the service
status manually, when start / stop the service outside of systemd.
Thank you.
-- Original --
From: "Lennart Poettering";
Date: 2017??6??29??(??) 4:29
To: "Oliver Neuku
So, I've got a piece of hardware I want to do a final handover to just
around reboot.target / shutdown.target
This will then cause the entire CPU and hardware allocated to it to
actually drop power (and schedule re-power), so I don't want to do this
earlier.
Is it simply to do:
[Unit]
DefaultD
15 matches
Mail list logo
