Yeah I think that's what I might end up doing...and if it comes down to it, that will be fine. Thanks for the suggestion! -Erik Quoting Brady Hegberg <bradyh at bitstream.net>: > This may be a somewhat inelegant idea but you could create a "common" > directory in each customer's root and then run a cronjob that > synchronizes them all periodically. > > Brady > > > Hi all - I'm trying to set up an ftp server to allow our customers to > > download softwarem, updates, yada yada, > > > > The idea is to, upon login, dump the users into their chrooted home dir, > > which would contain some of our custom software, writted specifically > > for them. This was easy to do.....now comes the catch: > > > > We want to also give them access to a "Common" directory as well. Any > > ideas? > > > > I've thought about structuring the ftp tree as follows: > > /Common > > /cust1 > > /cust2 > > /cust3 > > giving the customer only read access to their folder and the Common > > folder....however, the management doesn't like the idea of presenting > > our list of customers to the whole world. Soooo... > > > > Here was my second strategy: > > /Common > > /cust1 > > |_ symlink to Common > > /cust2 > > |_ symling to Common > > > > etc etc.....well that didn't work since the users were chrooted to their > > home dirs. > > > > I'm stumped! > > > > Thanks- > > Erik Anderson > > > > _______________________________________________ > > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, > Minnesota > > http://www.mn-linux.org tclug-list at mn-linux.org > > https://mailman.mn-linux.org/mailman/listinfo/tclug-list > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, > Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list > -- Erik Anderson - erik at andersonfam.org