Andrei Borzenkov wrote:

Отправлено с iPhone

...

3 марта 2016 г., в 7:56, Linda Walsh написал(а):

I was looking over the services in my sysd dir, and notice that some of them end with an '@' sign for no _apparent_ reason:

sys/arpwatch@.service* sys/mdmon@.service sys/kmsconvt@.service sys/openvpn@.service sys/mdadm-grow-continue@.service sys/teamd@.service sys/mdadm-last-resort@.service sys/vpnc@.service sys/mdadm-last-resort@.timer sys/wacom-inputattach@.service

I currently have 122 service entries, with 9 services using '@', and 2 timers w/1 ending in @.

Anyone know why '@' is part of the name, or why it is even considered "a good thing" to include '@' as part of a service name (that isn't a "service@location")?

Those are unit templates, see "man systemd.unit"

I.e. they need an instance name. I've only had reason to run one vpn, so that's openvpn@openvpn, but I frequently run multiple postfix instances - postfix@inst1, postfix@inst2 etc. etc. -- Per Jessen, Zürich (1.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

Those are unit templates, see "man systemd.unit"

--- Doi! Tnx for the pointer... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

On 03/02/2016 11:56 PM, Linda Walsh wrote:

...

I was looking over the services in my sysd dir, and notice that some of them end with an '@' sign for no _apparent_ reason:

sys/arpwatch@.service* sys/mdmon@.service sys/kmsconvt@.service sys/openvpn@.service sys/mdadm-grow-continue@.service sys/teamd@.service sys/mdadm-last-resort@.service sys/vpnc@.service sys/mdadm-last-resort@.timer sys/wacom-inputattach@.service

I currently have 122 service entries, with 9 services using '@', and 2 timers w/1 ending in @.

I don't have those. What package do the come with?

rpm -e mdadm-3.3.1-5.3.1.x86_64 error: Failed dependencies: mdadm >= 3.3 is needed by (installed) libstorage5-2.25.18-3.1.x86_64 rpm -e libstorage5 error: Failed dependencies:

-- ran the attached script in the relevant dir, which is really a symlink: Ishtar:law/bin/sys/sys> /bin/pwd /usr/lib/systemd/system Ishtar:law/bin/sys/sys> /tmp/rpm_n_dist Dist Path Rpm ---- ---- --- 13.2, arpwatch@.service, arpwatch-2.1a15-157.1.3.x86_64 13.2, kmsconvt@.service, kmscon-8-2.1.4.x86_64 13.2, mdadm-grow-continue@.service, mdadm-3.3.1-5.3.1.x86_64 13.2, mdadm-last-resort@.service, mdadm-3.3.1-5.3.1.x86_64 13.2, mdadm-last-resort@.timer, mdadm-3.3.1-5.3.1.x86_64 13.2, mdmon@.service, mdadm-3.3.1-5.3.1.x86_64 13.2, openvpn@.service, openvpn-2.3.4-2.7.1.x86_64 13.2, teamd@.service, libteam-tools-1.11-2.1.4.x86_64 13.2, vpnc@.service, vpnc-0.5.3r517-9.2.1.x86_64 13.2, wacom-inputattach@.service, xf86-input-wacom-0.24.0-2.1.4.x86_64 --- Am mildly surprised you don't have any of those installed -- since some seem to be required for a working system, like: libstorage.so.5()(64bit) is needed by (installed) libstorage-ruby-2.25.18-3.1.x86_64 libstorage.so.5()(64bit) is needed by (installed) yast2-storage-3.1.50-4.1.x86_64 libstorage5 = 2.25.18 is needed by (installed) libstorage-ruby-2.25.18-3.1.x86_64 libstorage5 >= 2.25.18 is needed by (installed) yast2-storage-3.1.50-4.1.x86_64

rpm -e yast2-storage error: Failed dependencies: yast2-storage >= 2.21.11 is needed by (installed) yast2-network-3.1.104-1.3.x86_64 yast2-storage is needed by (installed) yast2-reipl-3.1.4-2.1.9.noarch yast2-storage >= 2.16.1 is needed by (installed) yast2-add-on-3.1.9-1.9.noarch yast2-storage is needed by (installed) yast2-live-installer-3.1.3-2.1.10.noarch yast2-storage is needed by (installed) autoyast2-installation-3.1.66-1.1.noarch yast2-storage >= 2.24.1 is needed by (installed) yast2-installation-3.1.116-1.6.noarch yast2-storage >= 2.22.9 is needed by (installed) yast2-update-3.1.23-1.7.x86_64 yast2-storage >= 2.18.18 is needed by (installed) yast2-bootloader-3.1.101a-5.1.x86_64 yast2-storage is needed by (installed) yast2-kdump-3.1.19-1.8.x86_64

---- What type of system are you running on that doesn't use yast? The others have similarly long nested lists of requirements -- I don't see how you could have a 13.2 installed and not have any of those -- nor do I find it likely all of those dependencies would be disappearing in Leap... Are you sure your system is "integrous" ? ;-) impossible #!/bin/bash -u shopt -s expand_aliases alias my=declare int=my\ -i sub=function declare base=$(/bin/pwd) readarray -t pathnames< <('ls' -1 *@.*) readarray -t rpms< <(for p in "${pathnames[@]}";do rpm -qf "$base/$p"; done) readarray -t dist< <(for r in "${rpms[@]}"; do rpm -qi "$r"|grep Dist|print_field_n 3; done) sub max_len () { my ar_p="$1" ; shift int max=0 my p="" for p in $(eval "echo \"\${$ar_p[@]}\""); do ((${#p}>$max)) && max=${#p} done echo $max } int dml=1+$(max_len dist) int pml=1+$(max_len pathnames) int rml=$(max_len rpms) int i=0 printf "%-*s %-*s %s\n" "$dml" Dist "$pml" Path Rpm printf "%-*s %-*s %s\n" "$dml" ---- "$pml" ---- --- for ((i=0;i<${#pathnames[@]};++i)) do printf "%-*s %-*s %s\n" "$dml" "${dist[i]}," \ "$pml" "${pathnames[i]}," "${rpms[i]}" done