I installed FFP Samba because I wanted a bit more control than the device's Samba gave me. All worked well for quite a while.
Now, for some reason, it appears that the device no longer appreciates me trying to infringe on its territory and somehow manages to kill FFP Samba and re-start its own version shortly after I try to start the FFP Samba.
I have the following in my /ffp/start/samba.sh:
#!/ffp/bin/sh
# PROVIDE: samba
# REQUIRE: LOGIN
. /ffp/etc/ffp.subr
name="samba"
start_cmd="samba_start"
stop_cmd="samba_stop"
status_cmd="samba_status"
required_files="/etc/samba/smb.conf"
smbd_flags="-D -s $required_files"
nmbd_flags="-D -s $required_files"
samba_start()
{
cp /ffp/etc/samba/smb.conf /etc/samba/
proc_start /ffp/sbin/smbd # /usr/sbin/samba/smbd
proc_start /ffp/sbin/nmbd # /usr/sbin/samba/nmbd
}
samba_stop()
{
# smb stop # I thought this would help, but it didn't
proc_stop smbd
proc_stop nmbd
}
samba_status()
{
proc_status smbd
proc_status nmbd
}
run_rc_command "$1"
It seems that as soon as I try to access one of my Samba shares (via one of my Windows machines), I can see it read the folder list and try to display the files, but then the old Samba takes over and I no longer see any files and if I try to access any of the shares again, I start getting "\\NAS\share is not accessible" errors (since the old Samba doesn't seem to like the Guest account I've configured).
I can verify that the old Samba is running instead of the FFP Samba with the top command.