Re: [systemd-devel] Unit dovecot.service has failed

I’m sorry for my poor English and misunderstanding. I’ve created a new account and post a new ticket. Thanks again. > 2019/10/07 18:47、Reindl Harald のメール: > > jesus that was a sample bugreport, in that case for Fedora > > just write a new one for RHEL at https://bugzilla.redhat.com/

Re: [systemd-devel] Journalctl --list-boots problem

Run both with SYSTEMD_LOG_LEVEL=debug in the environment and compare. Does your /etc/machine-id remain the same across boots? On Mon, Oct 7, 2019, 20:32 Martin Townsend wrote: > Hi, > > I'm trying to get journalctl --list-boots working but it always shows > the current boot > > # journalctl

Re: [systemd-devel] [systemd SELinux] system status permission

On 10/7/19 12:09 PM, Dominick Grift wrote: I tried it out with simple `systemctl status` Oct 07 19:04:21 myguest systemd[1]: Sent message type=method_return sender=org.freedesktop.systemd1 destination=n/a path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=a{sv} error-name=n/a

[systemd-devel] Journalctl --list-boots problem

Hi, I'm trying to get journalctl --list-boots working but it always shows the current boot # journalctl --list-boots 0 c064e8c1d1a2403f9370e550bb74ecb2 Mon 2019-10-07 17:02:44 UTC—Mon 2019-10-07 17:17:56 UTC I'm using persistent storage and I'm sure I have /var/log/journal setup correctly

Re: [systemd-devel] [systemd SELinux] system status permission

On Mon, Oct 07, 2019 at 06:51:57PM +0200, Dominick Grift wrote: > On Mon, Oct 07, 2019 at 11:03:44AM -0500, Ian Pilcher wrote: > > I am hitting this (non-fatal) denial when reloading a service via the > > systemd dbus API: > > > > > type=USER_AVC msg=audit(1570462081.809:743): pid=1 uid=0 > > >

Re: [systemd-devel] [systemd SELinux] system status permission

On Mon, Oct 07, 2019 at 11:03:44AM -0500, Ian Pilcher wrote: > I am hitting this (non-fatal) denial when reloading a service via the > systemd dbus API: > > > type=USER_AVC msg=audit(1570462081.809:743): pid=1 uid=0 > > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > > msg='avc:

Re: [systemd-devel] org.freedesktop.systemd1.manage-units - which unit?

On 10/7/19 4:30 AM, Colin Guthrie wrote: It's a nasty work around, but for me it was all wrapped up in a script rather than manually run, so it didn't matter too much really. You can adjust that to suit make it more tolerant to other arguments etc, but it's definitely no where near as nice or

[systemd-devel] [systemd SELinux] system status permission

I am hitting this (non-fatal) denial when reloading a service via the systemd dbus API: type=USER_AVC msg=audit(1570462081.809:743): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { status } for auid=n/a uid=0 gid=1001 cmdline="/usr/bin/python2

[systemd-devel] Unexpected behaviour not noticed by systemctl command

‐‐‐ Original Message ‐‐‐ On Monday, 7 October 2019 г., 13:48, Reindl Harald wrote: > > > Am 07.10.19 um 12:43 schrieb Andy Pieters: > > > Just lately ran into a fumble. I was trying to stop and disable a > > service and I typed in: > > systemctl stop --now example.service > > but

Re: [systemd-devel] Unexpected behaviour not noticed by systemctl command

On Mon, 7 Oct 2019 at 11:48, Reindl Harald wrote: > > > > Am 07.10.19 um 12:43 schrieb Andy Pieters: > > Just lately ran into a fumble. I was trying to stop and disable a > > service and I typed in: > > > > systemctl stop --now example.service > > but nowehere "disable" is statet with that

Re: [systemd-devel] Unexpected behaviour not noticed by systemctl command

Am 07.10.19 um 12:43 schrieb Andy Pieters: > Just lately ran into a fumble. I was trying to stop and disable a > service and I typed in: > > systemctl stop --now example.service but nowehere "disable" is statet with that command > The service duly stopped but wasn't disabled because the --now

[systemd-devel] Unexpected behaviour not noticed by systemctl command

Hi guys Just lately ran into a fumble. I was trying to stop and disable a service and I typed in: systemctl stop --now example.service The service duly stopped but wasn't disabled because the --now switch is only applicable on the disable/enable/mask commands However, shouldn't it be good

Re: [systemd-devel] Unit dovecot.service has failed

Am 07.10.19 um 10:16 schrieb Masaru Kitajima: > Hi, Mr. Harald. > > I went to see the page you told me, > https://bugzilla.redhat.com/show_bug.cgi?id=1748322 but I couldn't find > almost nothinh. > > But one thing I'm sure is I don't have service named "gssproxy." > > I have no idea... Do

Re: [systemd-devel] org.freedesktop.systemd1.manage-units - which unit?

Mantas Mikulėnas wrote on 02/10/2019 16:37: > On Wed, Oct 2, 2019 at 5:58 PM Ian Pilcher > wrote: > > On 9/26/19 11:49 AM, Mantas Mikulėnas wrote: > > In JS-based polkit rules, the action usually comes with 'unit' and > > 'verb' polkit variables --

Re: [systemd-devel] Make systemd-localed modify the kernel commandline for the initrd keymap?

Colin Walters wrote on 01/10/2019 20:33: > On Sun, Sep 29, 2019, at 6:08 AM, Lennart Poettering wrote: > >> i.e maybe write down a spec, that declares how to store settings >> shared between host OS, boot loader and early-boot kernel environment >> on systems that have no EFI NVRAM, and then we

Re: [systemd-devel] Unit dovecot.service has failed

Hi, Mr. Harald. I went to see the page you told me, https://bugzilla.redhat.com/show_bug.cgi?id=1748322 but I couldn't find almost nothinh. But one thing I'm sure is I don't have service named "gssproxy." I have no idea... Do you have any alternatice way? Blessing, Masaru > 2019/10/03