Re: [systemd-devel] Side effects of `systemctl daemon-reload`?

24.01.2018 21:33, Daniel Wang пишет: > I have cluster of 100s of nodes with systemd-232. To work-around a recently > discovered bug in systemd (https://github.com/systemd/systemd/issues/7798), > I want to deploy a timer to all my nodes that will check the number of > units and run `systemctl

[systemd-devel] Side effects of `systemctl daemon-reload`?

I have cluster of 100s of nodes with systemd-232. To work-around a recently discovered bug in systemd (https://github.com/systemd/systemd/issues/7798), I want to deploy a timer to all my nodes that will check the number of units and run `systemctl daemon-reload` once a certain threshold is hit

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Mi, 24.01.18 22:12, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 24.01.2018 22:08, Lennart Poettering пишет: > > On Mi, 24.01.18 22:01, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > 1;5002;0c > >> 24.01.2018 17:13, Lennart Poettering пишет: > >>> On Mi, 24.01.18 14:51, Thomas Blume

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

24.01.2018 22:08, Lennart Poettering пишет: > On Mi, 24.01.18 22:01, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 1;5002;0c >> 24.01.2018 17:13, Lennart Poettering пишет: >>> On Mi, 24.01.18 14:51, Thomas Blume (thomas.bl...@suse.com) wrote: >>> Would this be an acceptable approach? >>>

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Mi, 24.01.18 22:01, Andrei Borzenkov (arvidj...@gmail.com) wrote: 1;5002;0c > 24.01.2018 17:13, Lennart Poettering пишет: > > On Mi, 24.01.18 14:51, Thomas Blume (thomas.bl...@suse.com) wrote: > > > >> Would this be an acceptable approach? > > > > Since a long time there has been a proper API

Re: [systemd-devel] Side effects of `systemctl daemon-reload`?

On Mi, 24.01.18 10:33, Daniel Wang (wonder...@google.com) wrote: > I have cluster of 100s of nodes with systemd-232. To work-around a recently > discovered bug in systemd (https://github.com/systemd/systemd/issues/7798), > I want to deploy a timer to all my nodes that will check the number of >

[systemd-devel] systemctl is-active command returns inactive even if the unit does not exist

Hi folks, "systemctl is-active" command gives "inactive" no matter the unit exists and indeed inactive or it just not exist. This behavior is semantically true since a unit can never be active if it does not exist. But "systemctl is-enabled" command will give a clear result "Failed to get unit

Re: [systemd-devel] systemctl is-active command returns inactive even if the unit does not exist

On Thu, 25 Jan 2018, Kevin Hsu wrote: Hi folks, "systemctl is-active" command gives "inactive" no matter the unit exists and indeed inactive or it just not exist. This behavior is semantically true since a unit can never be active if it does not exist. But "systemctl is-enabled" command will

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Wed, 24 Jan 2018, Lennart Poettering wrote: You cannot lock device that does not exist. And as soon as it appears it is mounted. hu? Thomas' proposed approach of "systemctl lock $DEVICE" also requires there to be a known path for a device, hence it must already be plugged in already? Not

Re: [systemd-devel] Unclear behavior of tmpfiles.d "f" type

On 01/24/2018 05:16 AM, Lennart Poettering wrote: > Yes, I agree. I think the current O_APPEND behaviour indeed does not > make much sense, and O_EXIST would make more sense and actually be > in line with what the documentation suggests. > > I have thus prepared a PR that fixes this and makes it

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Di, 23.01.18 16:54, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.01.2018 um 16:49 schrieb Simon McVittie: > > On Tue, 23 Jan 2018 at 15:47:21 +0100, Franck Bui wrote: > > > Basically, systemd mounts all filesystems listed in /etc/fstab (unless > > > "noauto" is used) which is

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Tue, 23 Jan 2018, Simon McVittie wrote: I'm not sure why the old behavior is not compatible with modern storage The traditional behaviour requires you to have a well-defined point during boot at which you know that all hardware that was attached at power-on has been detected, and all

Re: [systemd-devel] date ranges with systemd-journal-gatewayd

On Wed, Jan 24 2018, Lennart Poettering wrote: > On Mi, 10.01.18 16:46, Jameson Graef Rollins (jroll...@finestructure.net) > wrote: > >> Hello. Is it possible to specify date ranges with >> systemd-journal-gatewayd (i.e. equivalent of --since= and --until= in >>

Re: [systemd-devel] SSL handshake error from offlineimap when using systemd to initialize

Am 24.01.2018 um 08:13 schrieb Yubin Ruan: On Tue, Jan 23, 2018 at 04:10:10PM +0100, Lennart Poettering wrote: On Di, 23.01.18 09:09, Reindl Harald (h.rei...@thelounge.net) wrote: depeding on how your network is configured use "network.service" or "networkmanager.service" (or however the

Re: [systemd-devel] SSL handshake error from offlineimap when using systemd to initialize

On Wed, Jan 24, 2018 at 08:57:18AM +0100, Reindl Harald wrote: > > > Am 24.01.2018 um 08:13 schrieb Yubin Ruan: > > On Tue, Jan 23, 2018 at 04:10:10PM +0100, Lennart Poettering wrote: > > > On Di, 23.01.18 09:09, Reindl Harald (h.rei...@thelounge.net) wrote: > > > > depeding on how your network

Re: [systemd-devel] systemd-journald missing crash logs

On So, 21.01.18 19:53, Farzad Panahi (farzad.pan...@gmail.com) wrote: > > On Fr, 12.01.18 16:13, Farzad Panahi (farzad.pan...@gmail.com) wrote: > > > > > I am running Arch-ARM on RPi3. I have noticed when system crashes I > > cannot > > > find any related crash log in journal logs. > > > > What

Re: [systemd-devel] SSL handshake error from offlineimap when using systemd to initialize

Am 24.01.2018 um 09:59 schrieb Yubin Ruan: On Wed, Jan 24, 2018 at 08:57:18AM +0100, Reindl Harald wrote: Am 24.01.2018 um 08:13 schrieb Yubin Ruan: On Tue, Jan 23, 2018 at 04:10:10PM +0100, Lennart Poettering wrote: On Di, 23.01.18 09:09, Reindl Harald (h.rei...@thelounge.net) wrote:

Re: [systemd-devel] Unclear behavior of tmpfiles.d "f" type

On Mo, 15.01.18 15:34, Eli Schwartz (eschwa...@archlinux.org) wrote: > Over in Arch Linux, I am trying to move some packages over from using > post-install scripts to using tpmfiles.d/sysusers.d for any applicable > behavior. Occasionally, default files need to be created with the > contents of

Re: [systemd-devel] Trouble with speed/mode in .link files

On Di, 02.01.18 13:32, Bruce A. Johnson (bjohn...@blueridgenetworks.com) wrote: > I've been trying for a few days to figure out how to set Ethernet speed > and mode using a .link file, and I can't figure out what I'm doing > wrong.  I've got a renamed interface ("eth2" -> "en01"), and ethtool >

Re: [systemd-devel] how is systemd-journal-gatewayd filtering logs?

On Mi, 10.01.18 19:03, Jameson Graef Rollins (jroll...@finestructure.net) wrote: > Hello, I'm having another systemd-journal-gatewayd issue... > > I'm finding that journal-gatewayd is not returning all logs that are > actually available in the journal to users with appropriate privileges. > >

Re: [systemd-devel] date ranges with systemd-journal-gatewayd

On Mi, 10.01.18 16:46, Jameson Graef Rollins (jroll...@finestructure.net) wrote: > Hello. Is it possible to specify date ranges with > systemd-journal-gatewayd (i.e. equivalent of --since= and --until= in > journalctl)? I see there is a "Range:" header option that allows > restricting entries

Re: [systemd-devel] Is it a bug of manager->n_on_console?

On Mo, 25.12.17 13:31, piliu (pi...@redhat.com) wrote: > Hi, > > When debugging with a shell, manager_status_printf() always prints "A > start job...". After tracing the systemd's code, I found in that > function, the cond "if (type == STATUS_TYPE_EPHEMERAL && m && > m->n_on_console > 0)" does

Re: [systemd-devel] question about socket activation

On Fr, 29.12.17 17:19, eshark (eshar...@163.com) wrote: > Hi, All > I tried to test the socket activation by a simple foobar.socket and > foobar.service, which are as the following: > foobar.socket: >[Socket] >ListenStream=/dev/socket/foobar > > >[Install]

Re: [systemd-devel] Dependencies on DBus activated services during shutdown

On Mo, 08.01.18 16:07, Michal Koutný (mkou...@suse.com) wrote: > Hello, > I'd like to ask your opinion on the following situation. > > B.service exposes its API through D-Bus. A.service uses this API and > thus it has a dependency on B.service. This is implicit though -- and > we're happy we can

Re: [systemd-devel] Multiple services using the same core service?

On Di, 26.12.17 01:39, 林自均 (johnl...@gmail.com) wrote: > Hi folks, > > I am trying to achieve: > > # systemctl start sshd-shell.service (1) > # systemctl start sshd-sftp.service (2) > # systemctl stop sshd-shell.service (3) > # systemctl stop sshd-sftp.service (4) > > Before

Re: [systemd-devel] How to add filter for ActiveState property and get to know for which object this property is?

On Di, 16.01.18 16:13, Tomasz Michalski (tmichalsk...@gmail.com) wrote: > And I have other question. Generally we wonder what will be better design > for monitoring systemd services > 1.) > - add-match to ActiveState > - subscribe to systemd1.Manager > - then we have to start in separate thread

Re: [systemd-devel] how to know what exactly parameter set in busCtl methods?

On Di, 16.01.18 12:52, Tomasz Michalski (tmichalsk...@gmail.com) wrote: > Hi > I have a problem with call methods from terminal which take an argument, > for example when I try to use this one: > busctl call org.freedesktop.systemd1 > /org/freedesktop/systemd1/unit/syscom_2epath

Re: [systemd-devel] How to add filter for ActiveState property and get to know for which object this property is?

On Di, 16.01.18 15:41, Tomasz Michalski (tmichalsk...@gmail.com) wrote: > Handler: > int propertiesChangedHandler(sd_bus_message *message, void *userdata, > sd_bus_error *error) > { > const char *data; > const char *path; > int r = 0; > > if(!message) > printf("Empty

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Mi, 24.01.18 14:51, Thomas Blume (thomas.bl...@suse.com) wrote: > Would this be an acceptable approach? Since a long time there has been a proper API for this: just take a BSD file lock on the device node and udev won't bother with the device anymore. As soon as you close the device fully

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

On Di, 23.01.18 15:47, Franck Bui (f...@suse.de) wrote: > Hi, > > I'm resurrecting an old but recurrent issue here which I'd like to > clarify one more time. > > Basically, systemd mounts all filesystems listed in /etc/fstab (unless > "noauto" is used) which is good since that's how fstab was