Clarification:
1) You want to build out config files based upon a central config
repo. This is what cfengine and it's fellows are for.
2) ISCSI is for mounting file systems over your network. My favorite
example is to show how all the devices for my servers are ISCSI from
my SANs.
I am not suggesting mounting a filesystem over a wide area to give
targets for file copying scripts. I am saying: do not synchronize
your configuration of services across servers by copying config files
around. That is not to say it will not work. Just that it is totally
inelegant and will be a pain to maintain as time goes on and services
are added to that list. More of a real world growth problem that has
been solved 10 ways to Sunday already.
On Tue, Jan 6, 2009 at 11:29 AM, Jeremy (mailing list box)
<listbox@unix-boy.com> wrote:
> John Souvestre wrote:
>>
>> Hi.
>>
>> I have two situations in which sharing the file system on a Linux box
>> would be
>> handy. I'm looking at NFS, Samba and SSHFS. Any others I should be
>> considering?
>>
>
> Wow, surprised no one else has said this yet, but are IPSEC tunnels out of
> the question ? Once you have the IPSEC tunnels in place, you can run SAMBA
> or, theoretically, NFS over them.
>
> J
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 01/06/09
This archive was generated by hypermail 2.2.0 : 02/17/09 EST