On Fri, 20 Nov 2009 at 1:19pm, J. Bruce Fields wrote > I'm assuming /export and /export/qb3 are on the same filesystem? > > In that case, adding a mountpoint at /export/qb3: > > mount --bind /export/qb3 /export/qb3 > > (and adding crossmnt on /export) will probably work around the problem. > > As stated elsewhere, this isn't really secure: an attacker with access > to the network will probably still be able to write to /export/. If > that's a problem, then you need qb3 to really be its own filesystem. This is exactly what I needed -- thanks for the pointer. I went with the 2nd option, and it works as it should. Thanks again. -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
