I've been able to fudge my way around SysV init.d for years, but I've
just run into a systemd brick wall. Googling hasn't been successfull in
finding a likely solution.
I installed Fedora 18 a while back, and then added samba, but when I
tried to activate it via the sytem/services gui winbond, nmb and smb do
not appear on the list.
The files winbind.service, nmb.service and smb.service appear in
/usr/lib/systemd/system
In fact, those are the only files that refer to them anywhere.
If I try to manually start them:
> sudo systemctl start /usr/lib/systemd/system/winbind.service
Failed to issue method call: Unit
usr-lib-systemd-system-winbind.service.mount failed to load: No such
file or directory. See system logs and 'systemctl status
usr-lib-systemd-system-winbind.service.mount' for details.
> sudo systemctl status usr-lib-systemd-system-winbind.service.mount
usr-lib-systemd-system-winbind.service.mount
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
> cat winbind
[Unit]
Description=Samba Winbind Daemon
After=syslog.target network.target nmb.service
[Service]
Type=forking
Environment=KRB5CCNAME=/run/samba/krb5cc_samba
PIDFile=/run/winbindd.pid
EnvironmentFile=-/etc/sysconfig/samba
ExecStart=/usr/sbin/winbindd "$WINBINDOPTIONS"
ExecReload=/usr/bin/kill -HUP $MAINPID
[Install]
WantedBy=multi-user.target
I know the basic samba install is good as I could invoke the three using
SysV scripts from FC14, but setting up all the rcx.d links as well as
the scripts didn't make them appear in the services list like it was
suggested in the systemd writeup I looked at.
Looking at the initial install log (courtesy of anaconda) samba and
samba-client were installed then, but winbind was not. An FC17 set up
the same way has the same fault.
Does anyone have suggestions? Given two separate installs have gone the
same way there must be something wrong with what I'm doing.
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main
