coreos / fedora-coreos-pinger

Telemetry service to be used in Fedora CoreOS (see https://github.com/coreos/fedora-coreos-tracker/issues/86)
Apache License 2.0
15 stars 7 forks source link

fedora-coreos-pinger username is too long #21

Closed bgilbert closed 5 years ago

bgilbert commented 5 years ago

The fedora-coreos-pinger user and group names are so long that they cause filenames in ls -l to wrap on an 80-character terminal:

[core@localhost ~]$ ls -al /run
total 24
drwxr-xr-x. 30 root                 root                  860 Aug  7 11:02 .
drwxr-xr-x. 12 root                 root                  253 Aug  1 13:57 ..
-rw-------.  1 root                 root                    0 Aug  7 11:02 agett
y.reload
drwxr-x---.  2 chrony               chrony                 80 Aug  7 11:02 chron
y
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 conso
le
drwxr-xr-x.  4 root                 root                  100 Aug  7 11:02 conso
le-login-helper-messages
drwx------.  2 root                 root                   40 Aug  7 11:02 crypt
setup
drwxr-xr-x.  2 root                 root                   60 Aug  7 11:02 dbus
-rw-r--r--.  1 root                 root                    4 Aug  7 11:02 dhcli
ent-eth0.pid
prw-------.  1 root                 root                    0 Aug  7 11:02 dmeve
ntd-client
prw-------.  1 root                 root                    0 Aug  7 11:02 dmeve
ntd-server
srw-rw----.  1 root                 docker                  0 Aug  7 11:02 docke
r.sock
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 faill
ock
drwxrwxr-x.  3 fedora-coreos-pinger fedora-coreos-pinger   60 Aug  7 11:02 fedor
a-coreos-pinger
drwxr-xr-x.  2 root                 root                   60 Aug  7 11:02 fsck
-rw-r--r--.  1 root                 root                   17 Aug  7 11:02 ignit
ion.env
prw-------.  1 root                 root                    0 Aug  7 11:02 initc
tl
drwxr-xr-x.  4 root                 root                  100 Aug  7 11:02 initr
amfs
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 issue
.d
drwxr-xr-x.  5 root                 root                  100 Aug  7 11:02 lock
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 log
drwx------.  2 root                 root                   80 Aug  7 11:02 lvm
-rw-r--r--.  1 root                 root                    4 Aug  7 11:02 lvmet
ad.pid
drwx--x---.  2 root                 root                   40 Aug  7 11:02 mdadm
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 media
-rw-r--r--.  1 root                 root                    0 Aug  7 11:02 motd
drwxr-xr-x.  2 root                 root                   60 Aug  7 11:02 motd.
d
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 mount
drwxr-xr-x.  4 root                 root                  140 Aug  7 11:02 Netwo
rkManager
-rw-r-----.  1 root                 root                    0 Aug  7 11:02 ostre
e-booted
drwx------.  2 root                 root                   40 Aug  7 11:02 podma
n
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 samba
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 seper
mit
drwxr-xr-x.  2 root                 root                   40 Aug  7 11:02 setra
ns
-rw-r--r--.  1 root                 root                    4 Aug  7 11:02 sshd.
pid
-rw-------.  1 root                 root                    4 Aug  7 11:02 sssd.
pid
drwx--x--x.  3 root                 root                   60 Aug  7 11:02 sudo
drwxr-xr-x. 17 root                 root                  420 Aug  7 11:02 syste
md
drwxr-xr-x.  2 root                 root                   60 Aug  7 11:02 tmpfi
les.d
drwxr-xr-x.  7 root                 root                  160 Aug  7 11:02 udev
drwxr-xr-x.  3 root                 root                   60 Aug  7 11:02 user
-rw-rw-r--.  1 root                 utmp                 1920 Aug  7 11:02 utmp
drwxrwxr-x.  4 zincati              zincati                80 Aug  7 11:02 zinca
ti
[core@localhost ~]$ 
jlebon commented 5 years ago

Maybe just fcos-pinger? The name of the file itself and the user's GECOS field at least should hopefully be enough already to know where it comes from.

rfairley commented 5 years ago

fcos-pinger SGTM - had this in mind too.