A fresh install of samba on cauldron systemctl reported that the smb.service was "masked" and so it was impossible to start smb unmasking smb.service made no difference The files: /usr/lib/systemd/system/smb.service /usr/lib/systemd/system/nmb.service were empty files I copied the two service files from an mga6 system and samba is now functioning correctly
Assigning to the registered maintainer.
CC: (none) => marja11Assignee: bugsquad => bgmilne
And CC'ing the last committer.
CC: (none) => bruno
The name of the template files changed in this version, and so the files generated were empty. I've fixed that and I'm making a build test before pushing it again.
Assignee: bgmilne => brunoStatus: NEW => ASSIGNED
Fixed with samba-4.9.1-2.mga7 currently building
This update does create the service files. However, there seems to be a problem: # systemctl status smb ● smb.service - Samba SMB Daemon Loaded: error (Reason: Exec format error) Active: inactive (dead) /usr/lib/systemd/system/smb.service:14: Executable path is not absolute: @SBINDIR@/smbd /usr/lib/systemd/system/smb.service:11: Not an absolute path, ignoring: @PIDDIR@/smbd.pid /usr/lib/systemd/system/smb.service:13: Path '-@SYSCONFDIR@/sysconfig/samba' is not absolute systemctl status nmb ● nmb.service - Samba NMB Daemon Loaded: error (Reason: Exec format error) Active: inactive (dead) Docs: man:nmbd(8) man:samba(7) man:smb.conf(5) /usr/lib/systemd/system/nmb.service:13: Executable path is not absolute: @SBINDIR@/nmbd /usr/lib/systemd/system/nmb.service:11: Not an absolute path, ignoring: @PIDDIR@/nmbd.pid /usr/lib/systemd/system/nmb.service:12: Path '-@SYSCONFDIR@/sysconfig/samba' is not absolute
Yeah, I think the correct thing would be to see if make_install can install the service files properly and dont need the cat/sed hack in spec anymore
CC: (none) => tmb
Summary: Samba - smb.service and nmb.service are empty files => Samba - smb.service and nmb.service don't start (was: smb.service and nmb.service are empty files)
*** Bug 23811 has been marked as a duplicate of this bug. ***
CC: (none) => jamagallon
@Thomas, you're right, there is now a possibility to do the right stuff for systemd in the configure options. I'm making tests with that to build it again and hopefully this time the unit files will be correctly handled.
samba-4.9.1-3.mga7 on its way to updates_testing with the new usage of option --systemd-install-services of configure to manage the systemd unit files. They look correct now.
With 4.9.1-3 samba is working normally for me. Thanks. Closed as fixed
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED