Hi,

I'm currently looking after an old SCO UNIX server that is running Samba to share files to a Windows server.

The issue is that the smbd service keeps stopping (currently diagnosing) but I wondered if it was possible to monitor when it is stopped and then automatically restart the service?

The client in question uses these servers 24/7 and it would be better to have it auto-start if it stops at 2AM to avoid down-time etc.

Any help is appreciated and thanks in advance.

Well, that's a bit vague and open-ended. Are they currently using any monitoring systems now, like Nagios or Zabbix?? They can use those to monitor/restart services if they've already got them, or a system like it. You can also write a script for the local machine that runs a periodic check on the service, to see if it's still going, and bounce it if not. Or, a script on a remote machine that uses SNMP to query the service, and issue a restart via some method (ssh command?).

And bear in mind that if the service is hung, those methods go right out the window...since the PROCESS is still there and alive, but not actually DOING anything. That's when monitoring gets interesting, and the solutions more creative.

Best thing I could suggest for you and your client is to get off that old SCO crap, and go to CentOS for Samba services. Heck, even a simple off-the-shelf NAS device that you can go buy will probably have better performance than the SCO system, and still provide *Nix/Windows sharing services.

Thanks TB0ne. I thought it may be a simple question so didn't add all of the details.

The script will probably be the best route as it does completely stop rather than hanging in a running state.

It's running an old PECAS system that will cost the client £120,000 to upgrade apparently so we're having to work with what we have.

Thanks again for the suggestions mate.

lol, they should have run an economic model simulation around replacement of obsolete equipment! (Or is it just me that finds it funny?)

Well, that's a simple script to write, and there are probably thousands of samples you can find on Google already, ready to modify to suit you.
No worries, you're welcome. But honestly, if Samba is the service you're worried about, why not leave the other services on that system alone, and just spring for a NAS? This:

http://www.newegg.com/Product/Produc...82E16822154587

...is $189. And a snappy 2TB hard disk is about $110. Supports NFS, Samba, FTP, and HTTP. Makes the problem go away cheaply. And if they can spend $500 or so, they can get hot-swappable disks and LOTS more capacity.