Re: [systemd-devel] how to debug failures when trying to lock down services

On Thu, Nov 30, 2017 at 5:27 AM, Michael Biebl wrote: > Hi, > > today I tried to lock down the rsyslog.service that I have on my system. > > For that I first created an override.conf that contained > > [Service] > ProtectHome=yes > PrivateTmp=yes > PrivateDevices=yes > >

Re: [systemd-devel] [QUESTION] AIX 7.1 nodes area not reporting

On Thu, Nov 30, 2017 at 7:19 AM, Vengatesh R wrote: > Hi Team, > > > > AIX 7.1 nodes area not reporting to puppet master. Please find the below > details. > > > > Puppet master : Red hat Linux 7.3 x86_64 > Hi, this is not the Puppet mailing list, not the AIX mailing

Re: [systemd-devel] Question about service dependency handling in systemd-228

Hi all, Thank you very much for your support. I will try to fix the cycle. Brs, On Mon, Nov 27, 2017 at 4:11 PM, Reindl Harald wrote: > > > Am 27.11.2017 um 05:23 schrieb Bao Nguyen: > >> Thanks all for your comments. I will try to use option FreeBind. However >>

[systemd-devel] [QUESTION] AIX 7.1 nodes area not reporting

Hi Team, AIX 7.1 nodes area not reporting to puppet master. Please find the below details. Puppet master : Red hat Linux 7.3 x86_64 The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. Any use

[systemd-devel] how to debug failures when trying to lock down services

Hi, today I tried to lock down the rsyslog.service that I have on my system. For that I first created an override.conf that contained [Service] ProtectHome=yes PrivateTmp=yes PrivateDevices=yes ProtectSystem=strict ReadWritePaths=/var/log ReadWritePaths=/var/spool/rsyslog

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

On Di, 28.11.17 12:14, Pekka Paalanen (ppaala...@gmail.com) wrote: > + > +[Unit] > +Description=Weston, a Wayland compositor, as a system service > +Documentation=man:weston(1) man:weston.ini(5) > +Documentation=http://wayland.freedesktop.org/ > + > +# Make sure we are started after logins are

Re: [systemd-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

On Mi, 29.11.17 16:38, Olaf Hering (o...@aepfle.de) wrote: > The detection of ConditionVirtualisation= relies on the presence of > /proc/xen/capabilities. If the file exists and contains the string > "control_d", the running system is a dom0 and VIRTUALIZATION_NONE should > be set. In case

Re: [systemd-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git

Re: [systemd-devel] blk_update_request

On Wed, Nov 29, 2017 at 6:28 PM, Dorian ROSSE wrote: > Dear IT worker, > > I have some red errors on the log: > > sd 2:0:0:0 [sdb] No Caching mode page found > sd 2:0:0:0 [sdb] Assumons drive cache: write through > ... > blk_update_request : I/O error, dev fd0,

[systemd-devel] blk_update_request

Dear IT worker, I have some red errors on the log: sd 2:0:0:0 [sdb] No Caching mode page found sd 2:0:0:0 [sdb] Assumons drive cache: write through ... blk_update_request : I/O error, dev fd0, sectorielle 0 ... ... ... Failed to mount /media/cle. ... ... ... iSCSI de mon with pid=1162 started !

Re: [systemd-devel] [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

On Wed, Nov 29, Jan Beulich wrote: > But in the description you talk about detect_vm() - by its name that > doesn't look to care about Dom0, but whether running on top of > _some_ hypervisor. dom0 has to be handled as "no virtualization" because it has access to all hardware, all services

Re: [systemd-devel] [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

>>> On 29.11.17 at 17:07, wrote: > On Wed, Nov 29, Jan Beulich wrote: > >> But in the description you talk about detect_vm() - by its name that >> doesn't look to care about Dom0, but whether running on top of >> _some_ hypervisor. > > dom0 has to be handled as "no

[systemd-devel] [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

>>> On 29.11.17 at 16:38, wrote: > The detection of ConditionVirtualisation= relies on the presence of > /proc/xen/capabilities. If the file exists and contains the string > "control_d", the running system is a dom0 and VIRTUALIZATION_NONE should > be set. In case /proc/xen

[systemd-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

The detection of ConditionVirtualisation= relies on the presence of /proc/xen/capabilities. If the file exists and contains the string "control_d", the running system is a dom0 and VIRTUALIZATION_NONE should be set. In case /proc/xen exists, or some sysfs files indicate "xen", VIRTUALIZATION_XEN

Re: [systemd-devel] [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

On Wed, Nov 29, Jan Beulich wrote: > With all of the above, was it considered to check /sys/hypervisor > alongside with or perhaps even in preference to /proc/xen? Yes. /proc/xen/capabilities is the one and only place that indicates a dom0. Olaf signature.asc Description: PGP signature

Re: [systemd-devel] [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

>>> On 29.11.17 at 16:54, wrote: > On Wed, Nov 29, Jan Beulich wrote: > >> With all of the above, was it considered to check /sys/hypervisor >> alongside with or perhaps even in preference to /proc/xen? > > Yes. > /proc/xen/capabilities is the one and only place that indicates a

Re: [systemd-devel] Spec for journalctl log entry data structure

November 29, 2017 1:27 PM, "Thomas Güttler" wrote: > is there a spec or docs about the datastructure of a log entry in journalctl? > > Which fields does a log record have? There's a handy man page:

Re: [systemd-devel] Spec for journalctl log entry data structure

On Wed, Nov 29, 2017 at 2:18 PM, Thomas Güttler < guettl...@thomas-guettler.de> wrote: > Hi, > > > is there a spec or docs about the datastructure of a log entry in > journalctl? > The binary on-disk format is documented here: https://www.freedesktop.org/wiki/Software/systemd/journal-files/

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

On Wed, 29 Nov 2017 14:06:25 +0200 Mantas Mikulėnas wrote: > On Wed, Nov 29, 2017 at 10:32 AM, Jérémy Rosen > wrote: > > > I had a quick glance but didn't actually test... > > > > 1) please open a pull request on github, you will have more feedback

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

On Wed, 29 Nov 2017 09:32:02 +0100 Jérémy Rosen wrote: > I had a quick glance but didn't actually test... > 2) you probably want to add Alias=display-manager.service, so it can > pull it other graphical services Hi, that sounds like a good idea. Thanks, pq (adding

[systemd-devel] Spec for journalctl log entry data structure

Hi, is there a spec or docs about the datastructure of a log entry in journalctl? Which fields does a log record have? Regards,   Thomas Güttler -- Thomas Guettler http://www.thomas-guettler.de/ I am looking for

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

On Wed, Nov 29, 2017 at 10:32 AM, Jérémy Rosen wrote: > I had a quick glance but didn't actually test... > > 1) please open a pull request on github, you will have more feedback that > way > I think it's supposed to be a patch for Weston on fd.o and only cc'd here to

Re: [systemd-devel] [PATCH v2] udev rules: add by-location symlinks to nvme devices

On Di, 28.11.17 22:00, charles.r...@dell.com (charles.r...@dell.com) wrote: > On systems with multiple 2.5-inch form factor PCIe SSD devices, locating the > physical drive can be made easier with symlinks that contain the drive bay > and slot information like this: The first version you

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

I had a quick glance but didn't actually test... 1) please open a pull request on github, you will have more feedback that way 2) you probably want to add Alias=display-manager.service, so it can pull it other graphical services Regards Jérémy On 28/11/2017 11:14, Pekka Paalanen wrote: