On Fri, 24 Feb 2017 16:50:23 +0100, R.S. wrote: >W dniu 2017-02-24 o 16:37, Lucas Rosalen pisze: > > I've also worked on a smaller shop where all users' directories were > defined in one single filesystem. In this case, we didn't use automount.
That's my setup: single (not so big) filesystem for all users. Not many users, USS not haeavily used. I agree with John. Automounting user directories makes it simpler. Set it up and forget about it. With all users in a single filesystem, someone still has to mkdir for new users that might use Unix. And when someone leaves, their directory needs to be deleted. An advantage of giving each user their own HFS or zFS is that their filesystem can be migrated. I've used Automount in another way too. I'm not in a sysprog role now, but when I was, it was my standard practice to create another clone of my target zone whenever I had something new to install. There were times when there were as many as five clones in progress, usually by different people. The target zone name would match the IPL volume and a qualifier for the filesystem. I would automount manage /service. There were two advantages of doing it that way. 1. I didn't have to worry about making sure that the correct filesystem was mounted at /service. In fact, I didn't even have to think about it. 2. Different people could run APPLY jobs to their zone without interfering with someone else. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
