UNIX for Advanced & Expert Users

Hello,

I've been tasked with migrating users from one linux server to another new linux server. This is how I was thinking of doing it:

1.) Open up an NFS connection between the two servers, cp -Rp /home/ to the new server and then append the old /etc/group & /etc/passwd to the existing files on the new server.

2.) I'll double check to see that no UID or GID will conflict, if so I'll deal with those problems on a one on one basis.

However, my problem is that many of my users are running httpd in their home directories, so when I migrate their accounts over, their daemons won't work. So, how do I fix this without having to re-install & configure 75 apaches? Is there a script out there that I don't know about. Have any of you done this before, and if substantially different or better than what I'm advocating, please advise.

Thanks.

VJ

I've done migration from linux to OpenBSD. They have got a lil bit different syntax in /etc/passwd file. Make sure you check on that. Everything else seems to me just fine with your algorithm.

I might be mistaken but how can you run 75 httpds on separtly on one box? As far as i understand you run just one server and it creates child process using config file. If this is the case then you just have to install just one httpd and edit and copy your old httpd.conf to a new box.

Regards

Thanks for the reply.

You can have a multitude of httpd running on your server, all owned by different users. Each user is "root" within their own directory. They can basically run whatever they want, within reason of course. HTTPD is no different. All that you need to do is specify a different port for each httpd, which you configure in your httpd.conf . On the servers I administer, students have their websites up and running where they have their resume, etc. This could be done via virtual directories, but once users have their webserver up and running, then they can basically do whatever they want without having to bug me.

Anyway, I do know that if I don't find an alternative, then once I port their home dirs over the new server, I'll have to recompile apache on each user account. That's going to suck big time.

Any suggestions on how to avoid this?Plz.

VJ