On Tue, 20 Jun 2006, Gomez, Daniel wrote: > Hello, > > Is it feasible to hijack the automounter and issue your own custom mount > command or must the automount program perform the actual "mount" call?
The path to "mount" is established at compile time. Not being able to hijack mount is probably considered good seurity practice. You would need to write a warpper around mount to check the filesystem given in the -t and issue the mount command of your choice or call the normal mount. I guess it would be possible to add a configure option to allow an alternate commands to be used for all mounting and umounting. That would take a bit of work though as the existing configure setup isn't designed allow for this. > > The reason why I am interested is that we are using the IBRIX parallel > filesystem and we wish to have some clients mount IBRIX exported shares > using it's own special "ibrix_lwmount" client mount command and > non-ibrix clients to use the normal automount process. The catch is we > want to use the same mountpoint under the control of autofs for both > ibrix and non-ibrix clients. > > Is this feat feasible? Any insight into how one might even approach this > problem would be helpful to me and maybe to the whole community of ibrix > users using linux. > > I will say, I was able to simply double mount seemingly ok, meaning I > allow the automount to mount the directory as it will under normal > circumstances for regular clients, but then I run the ibrix mount > command ontop of the same directory. At first I was also using the > special ibrix umount command before I stopped the autofs daemon, but it > seems if I don't umount the double mounted directory, autofs still > unmounts all directory keys under the parent mountpoint fine. Yep. You can stack mount points in 2.6. The only real requirement for autofs to be able to expire mounts is that they appear in /etc/mtab. _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
