:-) Excellent. The only other thing to watch out for is for the existence of the /dev/shm/repos_n folders, as they would be gone when (if) the box is bounced. All handled from my bash script invoked via xinetd & working nicely. Cheers, Beto
Larry Jones wrote: >Norberto Meijome writes: > > >>In this server box, I've got setup /dev/shm --a shared memory drive (aka >>RAM Drive). Is there any reason why setting >> >>LockDir=/dev/shm/ >> >>in my config files is a bad idea? All users can read/write to this area. >> >> > >No, as you suspected, it's a *good* idea. But I'd loose the trailing >slash. > > > >>Also, is there any problem if I use the same LockDir entry for several >>repositories? (all running on the same box) >> >> > >There's certainly a potential problem. I'd suggest using separate >directories in the same file system. For example, /dev/shm/repos1 and >/dev/shm/repos2. > >-Larry Jones > >It's going to be a long year. -- Calvin > > > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
