actually SADMS should be update to take into account the new upstart scripts and so on.. but you can fix this issue by writting a "dummy" /etc/init.d/samba script that mimics the behaviour of the old init.d scripts.
here is a sample "/etc/init.d/samba" that i tested on Ubuntu 10.04 Server with the standard sadms package (from ubuntu repositories).
I know it's a quick and dirty fix, but at least now I can easily join my active directory structure and use AD users to define share access rights!!
----------------------File: /etc/init.d/samba , should be made executable !! --------------------
#!/bin/bash
### BEGIN INIT INFO
# Provides: samba
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start samba at boot time
# Description: Enable service provided by daemon.
### END INIT INF
Hi,
actually SADMS should be update to take into account the new upstart scripts and so on.. but you can fix this issue by writting a "dummy" /etc/init.d/samba script that mimics the behaviour of the old init.d scripts.
here is a sample "/etc/init.d/samba" that i tested on Ubuntu 10.04 Server with the standard sadms package (from ubuntu repositories).
I know it's a quick and dirty fix, but at least now I can easily join my active directory structure and use AD users to define share access rights!!
------- ------- ------- -File: /etc/init.d/samba , should be made executable !! ------- ------- ------
#!/bin/bash
### BEGIN INIT INFO
# Provides: samba
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start samba at boot time
# Description: Enable service provided by daemon.
### END INIT INF
service smbd $*
service nmbd $*
exit 0 ------- ------- ------- ------- ------- ------- ------- ------- ------- -
-------