I have 2 servers setup in as high availability running multiple applications. Each application can run on either server and has their own file system that is shared. I read that I can use the "include" statement in the global section to call separate smb-XXX.conf files and have this working fine. My question is how, or if, I can start/stop the smb-XXX.conf files separately so that as an application moves between the HA servers so does the share.
Roach, Duane writes:> My question is how, or if, I can start/stop the smb-XXX.conf files > separately so that as an application moves between the HA servers so > does the share.You can include the smb-XXX.conf and just change the content through your HA monitoring application. We use a static smb.conf and a separate part that is managed via a web frontend. Whenever the included part changes, samba's config is updated automatically. You could also move the smb-XXX.conf in or out of place, or rename them, based on whether or not that particular server is active. The included file does not *need* to be present, it is only used if it is there. However, no matter your setup, IMHO the trigger for the changes should come from your HA setup. Regards, roel
Roel writes:> You could also move the smb-XXX.conf in or out of place, or renamethem,> based on whether or not that particular server is active. Theincluded file> does not *need* to be present, it is only used if it is there.I have been testing moving a smb-hatest.conf (net bios name SAMBAHATEST) in and out that is controlled by the HA software. While the smb-hatest.conf share (HA_Test)) becomes available I do have a problem. The original smb.conf (net bios name = SAMBATEST) is no longer available. When I try and map a drive to it show that it is not associated with a domain. Is it possible that the last entry in wins and that the others are over written? Both conf file have the realm and domains listed the same. Duane