Thanks for the quick reply, Andrei. It sounds like there is indeed a race
condition in my code then since there is nothing explicit in my
implementation of service A that makes it wait until it has processed the
method call from service B before it stops listening for method calls. Did
I get that
On Mon, 30.03.15 01:46, Jan Engelhardt (jeng...@inai.de) wrote:
Thread originated in
http://lists.opensuse.org/opensuse-factory/2015-03/msg00419.html
On Monday 2015-03-30 01:07, Jan Engelhardt wrote:
On Sunday 2015-03-29 20:24, Stefan Seifert wrote:
Some time in the last month
On Sun, 29.03.15 17:12, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've got a automount point for a daily USB backup job. Due to some
instabilities of early USB3 chipsets and early USB3 devices, the mounted
device sometimes wents offline and eventually comes back after a while but
On Thu, 26.03.15 13:56, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Thu, Mar 26, 2015 at 09:42:45AM +0100, Lennart Poettering wrote:
On Sun, 15.03.15 03:51, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
wrote:
On Sun, Mar 15, 2015 at 03:49:07AM +0100, Zbigniew
On Mon, 23.03.15 20:09, Chris Morgan (chmor...@gmail.com) wrote:
Hello.
I have a journal test that fails periodically. When observing the test
with journalctl -f in the cases that fail I don't see any journal
entries from the journalctl -f. I'm wondering if I'm hitting rate
limiting here
Lennart Poettering lenn...@poettering.net writes:
On Wed, 01.04.15 15:45, Jan Synacek (jsyna...@redhat.com) wrote:
I am also against this since chrooting is an implementation detail of
mock, nothing more, and the fact that mock's recursive deletion logic
cannot handle removal of
On Tue, 31.03.15 11:52, Shawn Landden (sh...@churchofgit.com) wrote:
---
src/systemctl/systemctl.c | 51
+++
1 file changed, 51 insertions(+)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 3158a38..bf279f9 100644
---
On Wed, 01.04.15 21:04, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 04/01/2015 02:37 PM, Lennart Poettering wrote:
Note that I intend to add more subvolume lines to tmpfiles even. For
example, I am pretty sure /home should be created as subvolume if it
doesn't exist already, and
On Thu, 02.04.15 08:59, Jan Synacek (jsyna...@redhat.com) wrote:
think that systemd shouldn't create them where it doesn't make
sense. I don't think that that's achievable with the current logic. Am I
missing something?
But why do you say when it doesn't make sense? Why do you think
Dear systemd folks,
does systemd provide an option to debug userspace services with, for
example, the instrumentation framework Valgrind [1] to find memory leaks
or analyze the memory usage in more detail?
If it does not, should such a feature be added? Would it be useful, to
just have a switch
Hi All,
Testing has shown that the default experience of trackpoints on different
model laptops differs quite a lot, from almost unusably fast, to just plain
unusably slow on some models.
It seems that before libinput people where using the huge amount of
configurability Xorg gives them to work
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s / T540
generation of Thinkpads, making them somewhat unsensitive by default, add a
hwdb entry to tweak the sensitivity setting.
The ThinkPad X200s is way way too slow by default and unless you push the
trackpoint quite hard
There is quite a wide spread in the delta events generated by trackpoints,
some generate deltas of 1-2 under normal use, while others generate deltas
from 1-20.
This commit adds a set of rules + a hwdb file which allows specifying a
per model TRACKPOINT_CONST_ACCEL value which can be used by the
The IBM / Lenovo trackpoints are special, they allow specifying a sensitivity
setting through a ps/2 command, which changes the range of the deltas send when
using the trackpoint. One some models with normal usage one only deltas
of 1 or 2 are send, resulting in there only being 2 mouse cursor
The trackpoint of the Dell Latitude E6400 is somewhat slow by default,
where as the trackpoint of the Dell Latitude D620 is much too fast by default,
set TRACKPOINT_CONST_ACCEL for both of them to adjust for this.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
hwdb/70-trackpoint.hwdb | 12
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now, and this is useful information to have
in various places, so make input_id aware of this and make it set
ID_INPUT_POINTING_STICK on trackpoints.
While adding support for querying properties,
On Mon, 30.03.15 01:12, Mirco Tischler (mt...@gmx.de) wrote:
However there's one difference between these relative triggers and
OnCalendar: you can only use Persistent= in combination with
OnCalendar. This means that if your timer elapses in 5 minutes and you
suspend your machine for an hour
On Wed, 01.04.15 18:22, Kurt von Laven (k...@endlessm.com) wrote:
Hello folks,
I am trying to ensure that my system DBus service has time to handle a DBus
method call before it shuts down. My DBus service is implemented as a
system systemd service; let's call it service A. It runs a
On Thu, 26.03.15 16:09, Jan Janssen (medhe...@web.de) wrote:
Heya,
Hmm, so we already support passing special reboot() parameters, and
this is done by manipulating a file in /run, without introducing any
new targets. To me it appears that boot-into-firmware-setup is
something hat should be
On Thu, 02.04.15 11:27, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
Dear systemd folks,
does systemd provide an option to debug userspace services with, for
example, the instrumentation framework Valgrind [1] to find memory leaks
or analyze the memory usage in more detail?
Lennart Poettering lenn...@poettering.net writes:
On Thu, 02.04.15 08:59, Jan Synacek (jsyna...@redhat.com) wrote:
think that systemd shouldn't create them where it doesn't make
sense. I don't think that that's achievable with the current logic. Am I
missing something?
But why do you
On Thu, 2 Apr 2015, Lennart Poettering wrote:
On Thu, 02.04.15 18:43, Dimitrios Apostolou (ji...@gmx.net) wrote:
Hello list,
I'm having trouble to auto-activate a unit on resume, after suspend-to-ram
or hibernation. The unit properly stops when suspending (because of
Conflicts=sleep.target),
hi, sorry for the delay.
from
http://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html:
By default, it will wait for all links it is aware of and which are
managed by systemd-networkd.service(8) to be fully configured or
failed, *and for at least one link to
On Thu, Apr 2, 2015 at 3:08 PM, Nick Owens misch...@offblast.org wrote:
hi, sorry for the delay.
from
http://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html:
By default, it will wait for all links it is aware of and which are
managed by
Hi,
I have a problem with a timer that trigges a service that has a condition set.
The timer defines the following properties:
[Timer]
OnBootSec=1h
OnUnitInactiveSec=1h
Unit=autobackup@%i.service
The service unit set the following condition:
ConditionACPower=true
When I'm now on AC
On Thu, 02.04.15 13:55, Mantas Mikulėnas (graw...@gmail.com) wrote:
Isn't log_warning_errno(errno, %m) identical to just log_warning(%m)?
it's not. the former generates an ERRNO= structured journal field, the
latter doesn't. Also see my reply to Tom's review about this.
Lennart
--
Lennart
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now, and this is useful information to have
in various places, so make input_id aware of this and make it set
Hi,
On 02-04-15 12:21, Lennart Poettering wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now, and this is useful information to have
in various places, so make input_id
On Thu, Apr 2, 2015 at 1:54 PM, Lennart Poettering lenn...@poettering.net
wrote:
On Sun, 22.03.15 13:36, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
Love this work!
init_autofs_dev_ioctl(param);
param.ioctlfd = ioctl_fd;
-param.timeout.timeout = sec;
+
On Thu, 02.04.15 13:00, Michael Biebl (mbi...@gmail.com) wrote:
2015-04-02 11:06 GMT+02:00 Lennart Poettering lenn...@poettering.net:
If you want to ensure that bus communication still works in your
shutdown code, you hence need to make sure you place
After=dbus.service in your services,
2015-04-02 13:03 GMT+02:00 Lennart Poettering lenn...@poettering.net:
On Thu, 02.04.15 13:00, Michael Biebl (mbi...@gmail.com) wrote:
2015-04-02 11:06 GMT+02:00 Lennart Poettering lenn...@poettering.net:
If you want to ensure that bus communication still works in your
shutdown code, you
On 04/02/2015 08:31 AM, Lennart Poettering wrote:
On Wed, 01.04.15 21:04, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 04/01/2015 02:37 PM, Lennart Poettering wrote:
Note that I intend to add more subvolume lines to tmpfiles even. For
example, I am pretty sure /home should be
On Mon, 23.03.15 04:44, Shawn Landden (sh...@churchofgit.com) wrote:
Also allow getting time from time(2) when BUS_TRANSPORT_MACHINE.
v2: check for error
---
src/timedate/timedatectl.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
On Sun, 22.03.15 13:36, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
Love this work!
init_autofs_dev_ioctl(param);
param.ioctlfd = ioctl_fd;
-param.timeout.timeout = sec;
+
+/* Convert to seconds, rounding up. */
+param.timeout.timeout = usec
2015-04-02 11:06 GMT+02:00 Lennart Poettering lenn...@poettering.net:
If you want to ensure that bus communication still works in your
shutdown code, you hence need to make sure you place
After=dbus.service in your services, so that you are shut down before
dbus is.
Type=dbus service
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
+# Same as below but also sets the TPPS/2 IBM TrackPoint driver sensitivity
+KERNELS==input*, ATTR{device/name}==TPPS/2 IBM TrackPoint, \
+ IMPORT{builtin}=hwdb
'trackpoint:name:$attr{device/name}:$attr{[dmi/id]modalias}', \
Hi,
On 02-04-15 12:23, Lennart Poettering wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
+# Same as below but also sets the TPPS/2 IBM TrackPoint driver sensitivity
+KERNELS==input*, ATTR{device/name}==TPPS/2 IBM TrackPoint, \
+ IMPORT{builtin}=hwdb
Hi,
On 02-04-15 12:27, Lennart Poettering wrote:
On Thu, 02.04.15 12:21, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while
On Fri, 27.03.15 12:36, Tom Gundersen (t...@jklm.no) wrote:
+if (errno != EAGAIN)
+log_error_errno(errno, failed to expire automount: %m);
No need for this, it is equivalent to
log_error(failed to exprie automount: %m);
Not true really.
On Thu, 02.04.15 12:21, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now, and this is useful information to have
in
On Thu, 02.04.15 12:42, Hans de Goede (hdego...@redhat.com) wrote:
Hi,
On 02-04-15 12:23, Lennart Poettering wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
+# Same as below but also sets the TPPS/2 IBM TrackPoint driver sensitivity
+KERNELS==input*,
On Thursday 2015-04-02 10:35, Lennart Poettering wrote:
On Mon, 30.03.15 01:46, Jan Engelhardt (jeng...@inai.de) wrote:
What does systemctl status and systemctl show say about the unit
in question?
(And what is klog.service? Sounds really obsolete...)
The issue is not reproducible. Further
Dear systemd folks,
some network cards with certain cables and devices take up to five
seconds so that the link is up [1].
$ sudo journalctl -u systemd-networkd
-- Logs begin at Fr 2015-03-20 17:39:31 CET, end at So 2015-03-22
08:39:39 CET. --
Mär 20 17:39:31 myhostname
On Thu, 02.04.15 12:39, Hans de Goede (hdego...@redhat.com) wrote:
/* we must use this kernel-compatible implementation */
#define BITS_PER_LONG (sizeof(unsigned long) * 8)
#define NBITS(x) x)-1)/BITS_PER_LONG)+1)
@@ -131,6 +139,7 @@ static void test_pointers (struct udev_device
On Fri, Apr 3, 2015 at 6:55 AM, Kurt von Laven k...@endlessm.com wrote:
On a separate note, how long does systemd wait after sending a SIGTERM to a
service before sending it a SIGKILL?
http://www.freedesktop.org/software/systemd/man/systemd.kill.html
Hi!
On 25/03/15 14:36, Patrik Flykt wrote:
IFA_FLAGS is a discrete value and has no preprocessor #define defined for
it. Fix this by always using the value.
Seems that fix was not a real fix:
CC src/libsystemd/sd-id128/libsystemd_internal_la-sd-id128.lo
Actually I think I just answered my own question and in the process
realized that I didn't provide enough context in my original question.
There is a race condition in my code because when service B receives
SIGTERM, it calls g_dbus_connection_flush_sync
Am 02.04.2015 um 20:49 schrieb Al Lau:
As a test, the /usr/sbin/smartd $smartd_opts is invoked from the
command line and the daemon is forked and stayed up as expected. By
default, the /usr/sbin/smartd daemonize.
# cat /etc/sysconfig/smartmontools
smartd_opts=--interval=3600
В Thu, 2 Apr 2015 11:28:46 -0700
Al Lau laua...@gmail.com пишет:
The main process does not show up in the ps and only the forked process
shows up.
The systemd-cgls shows
│ ├─session-14613.scope
│ │ ├─ 1577 sshd: root@pts/4
│ │ ├─ 1676 -bash
│ │ ├─16792 systemctl start smartd
│
This method should greatly improve offset based lookup. We now don't have
to aggregate the full boot listing just so we can jump to a specific position,
which can be a real pain on big journals just for a mere -b -1 case.
As an additional benefit --list-boots should improve slightly too, because
On Thu, 02.04.15 14:33, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 04/02/2015 01:21 PM, Lennart Poettering wrote:
Well, I disagree. And yeah, I still think that /var/lib/machines
should be a subvolume, if it is not created manually as something else
before. I hear no convincing
On Thu, 02.04.15 13:07, Michael Biebl (mbi...@gmail.com) wrote:
2015-04-02 13:03 GMT+02:00 Lennart Poettering lenn...@poettering.net:
On Thu, 02.04.15 13:00, Michael Biebl (mbi...@gmail.com) wrote:
2015-04-02 11:06 GMT+02:00 Lennart Poettering lenn...@poettering.net:
If you want to
On Thu, 2015-04-02 at 15:04 +0100, Simon McVittie wrote:
On 02/04/15 14:31, Lennart Poettering wrote:
Hmm? I really don't see how the NFS vs wpa_supplicant issue has
anything to do with dbus? NFS doesn't care about dbus at all...
It does inasmuch as it requires networking to be up, which
On Thu, 02.04.15 12:31, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 04/01/2015 02:37 PM, Lennart Poettering wrote:
Note that I intend to add more subvolume lines to tmpfiles even. For
example, I am pretty sure /home should be created as subvolume if it
doesn't exist already, and
Lennart Poettering [2015-04-02 15:31 +0200]:
You need to order wpa_supplicant and NM Before=remote-fs-pre.target
and pull it it via Wants=remote-fs-pre.target. With that in place
during shutdown the mounts will be unmounted first, and NM/wpa only
shut down after that.
wpa_supplicant and NM
On Fri, 27.03.15 09:46, Shawn Landden (sh...@churchofgit.com) wrote:
I liked having the DST information. It is a pity glibc doesn't export
this information.
If TZDIR is set, glibc will look there rather than /usr/share/zoneinfo.
See tzset(3).
What's the rationale for this? Why would we
On Thu, 26.03.15 23:18, Shawn Landden (sh...@churchofgit.com) wrote:
On Thu, Mar 26, 2015 at 1:19 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 24.03.15 11:11, Shawn Landden (sh...@churchofgit.com) wrote:
Will result in slightly smaller binaries, and cuts out the branch,
On 02/04/15 14:31, Lennart Poettering wrote:
Hmm? I really don't see how the NFS vs wpa_supplicant issue has
anything to do with dbus? NFS doesn't care about dbus at all...
It does inasmuch as it requires networking to be up, which *might*
require dbus (e.g. for NetworkManager).
You need to
On 04/02/2015 01:21 PM, Lennart Poettering wrote:
Well, I disagree. And yeah, I still think that /var/lib/machines
should be a subvolume, if it is not created manually as something else
before. I hear no convincing case why it shouldn't be one.
I argue that we should default to directory
Hi,
On 2015-04-02 11:34, Lennart Poettering wrote:
On Thu, 26.03.15 16:09, Jan Janssen (medhe...@web.de) wrote:
Heya,
Hmm, so we already support passing special reboot() parameters, and
this is done by manipulating a file in /run, without introducing any
new targets. To me it appears that
Lennart Poettering [2015-04-02 13:03 +0200]:
Yeah, and rightfully so. I mean, a service really should be able to
shutdown if dbus is dead. In fact, it should be able to shutdown in
pretty much any situation...
They do, but that's irrelevant here. The problem is that dbus.service
shuts down
On Thu, 2015-04-02 at 16:31 +0200, Martin Pitt wrote:
Lennart Poettering [2015-04-02 15:31 +0200]:
You need to order wpa_supplicant and NM Before=remote-fs-pre.target
and pull it it via Wants=remote-fs-pre.target. With that in place
during shutdown the mounts will be unmounted first, and
On Thu, 02.04.15 11:11, Kai Krakow (hurikha...@gmail.com) wrote:
Hi!
Lennart Poettering lenn...@poettering.net schrieb am Do., 2. Apr. 2015 um
10:49 Uhr:
On Sun, 29.03.15 17:12, Kai Krakow (hurikha...@gmail.com) wrote:
Hello!
I've got a automount point for a daily USB backup
Hello list,
I'm having trouble to auto-activate a unit on resume, after suspend-to-ram
or hibernation. The unit properly stops when suspending (because of
Conflicts=sleep.target), but does not restart after resuming.
The key to achieve this as far as I understand, are the following two
Both services A and B specify Requires=dbus.service and After=dbus.service.
If I am interpreting everything that's being said correctly, there is a
race condition in my code since service A's implementation doesn't require
it to wait until it has processed the method call from service B before it
В Thu, 2 Apr 2015 18:43:40 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
Conflicts=sleep.target
WantedBy=multi-user.target sleep.target
These are mutually conflicting. One one hand Conflicts says to stop your
unit when sleep.target gets started, on the other hand WantedBy says to
start
On Thu, 2 Apr 2015, Andrei Borzenkov wrote:
В Thu, 2 Apr 2015 18:43:40 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
Conflicts=sleep.target
WantedBy=multi-user.target sleep.target
These are mutually conflicting. One one hand Conflicts says to stop your
unit when sleep.target gets
On Thu, 2 Apr 2015, Dimitrios Apostolou wrote:
On Thu, 2 Apr 2015, Andrei Borzenkov wrote:
В Thu, 2 Apr 2015 18:43:40 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
Conflicts=sleep.target
WantedBy=multi-user.target sleep.target
These are mutually conflicting. One one hand
On Thu, 02.04.15 10:43, Al Lau (laua...@gmail.com) wrote:
Hi,
I am seeking help and advise on troubleshooting the starting of the smartd
daemon. The /usr/sbin/smartd comes from the smartmontools version 6.3.
The /usr/lib/systemd/system/smartd.service file looks like this
# cat
On Thu, 02.04.15 18:43, Dimitrios Apostolou (ji...@gmx.net) wrote:
Hello list,
I'm having trouble to auto-activate a unit on resume, after suspend-to-ram
or hibernation. The unit properly stops when suspending (because of
Conflicts=sleep.target), but does not restart after resuming.
We do
As a test, the /usr/sbin/smartd $smartd_opts is invoked from the command
line and the daemon is forked and stayed up as expected. By default, the
/usr/sbin/smartd daemonize.
# cat /etc/sysconfig/smartmontools
smartd_opts=--interval=3600 --configfile=/etc/smartd.conf
From the /var/log/messages,
В Thu, 2 Apr 2015 19:34:55 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
On Thu, 2 Apr 2015, Dimitrios Apostolou wrote:
On Thu, 2 Apr 2015, Andrei Borzenkov wrote:
В Thu, 2 Apr 2015 18:43:40 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
Conflicts=sleep.target
On 04/02/2015 03:48 PM, Lennart Poettering wrote:
On Thu, 02.04.15 14:33, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 04/02/2015 01:21 PM, Lennart Poettering wrote:
Well, I disagree. And yeah, I still think that /var/lib/machines
should be a subvolume, if it is not created
On Thu, 2 Apr 2015, Andrei Borzenkov wrote:
В Thu, 2 Apr 2015 19:34:55 +0200 (CEST)
Dimitrios Apostolou ji...@gmx.net пишет:
On Thu, 2 Apr 2015, Dimitrios Apostolou wrote:
On Thu, 2 Apr 2015, Andrei Borzenkov wrote:
В Thu, 2 Apr 2015 18:43:40 +0200 (CEST)
Dimitrios Apostolou
On Thu, 02.04.15 15:51, Jan Janssen (medhe...@web.de) wrote:
Hi,
On 2015-04-02 11:34, Lennart Poettering wrote:
On Thu, 26.03.15 16:09, Jan Janssen (medhe...@web.de) wrote:
Heya,
Hmm, so we already support passing special reboot() parameters, and
this is done by manipulating a file in
On Thu, Apr 2, 2015 at 8:18 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Thu, 02.04.15 15:51, Jan Janssen (medhe...@web.de) wrote:
Hi,
On 2015-04-02 11:34, Lennart Poettering wrote:
On Thu, 26.03.15 16:09, Jan Janssen (medhe...@web.de) wrote:
Heya,
Hmm, so we already support
Hi,
I am seeking help and advise on troubleshooting the starting of the smartd
daemon. The /usr/sbin/smartd comes from the smartmontools version 6.3.
The /usr/lib/systemd/system/smartd.service file looks like this
# cat /usr/lib/systemd/system/smartd.service
[Unit]
Description=Self Monitoring
В Thu, 2 Apr 2015 10:43:00 -0700
Al Lau laua...@gmail.com пишет:
Hi,
I am seeking help and advise on troubleshooting the starting of the smartd
daemon. The /usr/sbin/smartd comes from the smartmontools version 6.3.
The /usr/lib/systemd/system/smartd.service file looks like this
# cat
I am seeking help and advise on troubleshooting the starting of the smartd
daemon. The /usr/sbin/smartd comes from the smartmontools version 6.3.
and the systemd unit si from where?
The /usr/lib/systemd/system/smartd.service file looks like this
and is wrong
# cat
The main process does not show up in the ps and only the forked process
shows up.
The systemd-cgls shows
│ ├─session-14613.scope
│ │ ├─ 1577 sshd: root@pts/4
│ │ ├─ 1676 -bash
│ │ ├─16792 systemctl start smartd
│ │ └─16793 /usr/bin/systemd-tty-ask-password-agent --watch
80 matches
Mail list logo
