32302 2016-07-22 17:44:59 +0300 Не включается автозапуск nfslock.service 2016-09-01 16:09:53 +0300 1 1 4 Development Sisyphus nfs-clients unstable all Linux CLOSED FIXED P3 normal --- 32420 1 cas sbolshakov evg sbolshakov qa-sisyphus oldest_to_newest 157735 0 cas 2016-07-22 17:44:59 +0300 cas ~ # systemctl enable nfslock.service Synchronizing state of nfslock.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable nfslock The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. 158391 1 sbolshakov 2016-09-01 16:09:53 +0300 в 1.3.4-alt1 rpc-statd.service включен в зависимости nfs-client.target