invoke-rc.d: unknown initscript, /etc/init.d/samba not found.

[LarryJ]

Binary package hint: system-config-samba

Apparently after you make a change in the gui of system-config-samba, scs attempts to restart samba using "/etc/init.d/samba". From what I know, the correct way to restart samba is with sudo service smbd restart or sudo restart smbd
sudo /etc/init.d/samba definitely doesn't work.

This shows up with Lucid 10.04 and system-config-samba version 1.2.63-0Ubuntu4

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: system-config-samba 1.2.63-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Dec 28 12:13:37 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: system-config-samba

[Matt Fischer (mfisch)]

Larry,

Thanks for filing this. I was looking through the bugs in here today and noticed that this one has been fixed by revision 1.2.63, which is the current version in precise (12.04). I did not back track and figure out where this was fixed. The latest code calls service, not the init.d script directly.

[Matt Fischer (mfisch)]

Larry, I was able to repro this today, so despite what I saw in the code, there is another hook that does call like you said, even in the latest version:

mfisch@caprica:/etc$ sudo system-config-samba

** WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
invoke-rc.d: unknown initscript, /etc/init.d/samba not found.
invoke-rc.d: unknown initscript, /etc/init.d/samba not found.
invoke-rc.d: unknown initscript, /etc/init.d/samba not found.
invoke-rc.d: unknown initscript, /etc/init.d/samba not found.

[Enkouyami (furyhamster)]

This bug still exists in Ubuntu 12.04.1 LTS.

[deschmit (deschmit)]

This bug still exists in Ubuntu 12.10