Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: Kingdomcome on November 25, 2009, 10:15:14 PM

Title: samba3 startup script
Post by: Kingdomcome on November 25, 2009, 10:15:14 PM

the startup script for samba3 leaves the config file /etc/samba/smb.conf as readonly.


Edit:  I would also like to request that starting of the server be removed to allow so that smb.conf can be restored from backup before starting.  Thanks

Title: Re: samba3 startup script
Post by: Jason W on November 25, 2009, 10:48:03 PM

The copying of the config file as a real file was an easy adjustment, hope Juanito doesn't mind that I went ahead and fixed. it as I have ample bandwidth and some time tonight..

Your mention of the starting of the server came after I began uploading, and of course I will leave that part for him to decide.

Title: Re: samba3 startup script
Post by: Kingdomcome on November 25, 2009, 11:17:32 PM

Ok.  Thanks!

Title: Re: samba3 startup script
Post by: Juanito on November 27, 2009, 04:24:36 AM

Thanks for sorting the smb.conf - in fact I had fixed it, but could never keep connected long enough to upload the 20+ mb to the repo...

I've been wondering for a while if we shouldn't have some kind of tinycore official/standard init.d file to start all extension with daemons/etc - I'm not too sure that this could take care of the "conf file in the backup" thing, but then again I don't recall noticing this as an issue with cups, etc?

Title: Re: samba3 startup script
Post by: Jason W on November 27, 2009, 08:36:00 AM

I am definitely in favor of using /usr/local/etc/init.d scripts to launch daemons, instead of using the /usr/local/tce.installed startup script.  The user is then in control of which services he wants running, and when to start it.

Title: Re: samba3 startup script
Post by: bmarkus on November 27, 2009, 08:49:55 AM

Quote from: Jason W on November 27, 2009, 08:36:00 AM

I am definitely in favor of using /usr/local/etc/init.d scripts to launch daemons, instead of using the /usr/local/tce.installed startup script.  The user is then in control of which services he wants running, and when to start it.

Agree. User can add scripts to bootlocal.sh to start wanted services. What is still missing is a similar script to accomodate shutdown scripts, see

http://forum.tinycorelinux.net/index.php?topic=4049.0

Title: Re: samba3 startup script
Post by: gerald_clark on November 27, 2009, 11:08:00 AM

A startup list could be used to start services, and read backwards, to stop them.

Title: Re: samba3 startup script
Post by: bmarkus on November 27, 2009, 11:20:48 AM

Quote from: gerald_clark on November 27, 2009, 11:08:00 AM

... and read backwards, to stop them.

Who and when?

Title: Re: samba3 startup script
Post by: gerald_clark on November 27, 2009, 11:39:12 AM

Instead of adding each service to bootlocal.sh, have a file such as services.lst.
Add each service you want started to services.lst in the order you need them started.
The system ( or bootlocal.sh ) runs "services start" which calls each listed init.d program with the start option.
On shutdown "services stop" is called which calls each listed program ( in reverse order ) with the stop option.