Sponsored Content
Top Forums UNIX for Advanced & Expert Users Migrating all users from one linux server to another... Post 8394 by vancouver_joe on Wednesday 10th of October 2001 11:01:27 PM
Old 10-11-2001
Migrating all users from one linux server to another...

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
 

9 More Discussions You Might Find Interesting

1. BSD

Migrating password file to new freebsd server

I need to migrate an existing master.passwd file to new FreeBsd Unix Box. I will moving from 4.1 to 6.1. I already have the home directories copied over. Once I copy over the masterpasswd file what do I need to do to make the system use the new master.passwd file? (0 Replies)
Discussion started by: rbizzell
0 Replies

2. AIX

Migrating AIX users to Linux

Hi all, I was wondering if anyone out there knew if it was possible to migrate users from AIX to Linux. What we want to do is install OpenLDAP on a Linux machine and port all the users over to LDAP. I've googled around and could only find a few things, such as mrgpwd - but that only comes... (0 Replies)
Discussion started by: djcronos
0 Replies

3. Ubuntu

Migrating from Unix to Linux

Is there a way to migrate username password from Freebsd 6.1 to Linux Ubuntu 8.04. I am using the server as a email server running postfix and using imap. Is there a way to transfer the usernames and password. I have transferred all the Maildirs but I am getting uid errors and gid errors even after... (2 Replies)
Discussion started by: rbizzell
2 Replies

4. AIX

Migrating a NIM Server to AIX 6.1

Guys, We are planning to upgrade one of our NIM server to AIX 6.1 from 5.3... Since the server itself is a NIM Server we can't perform it via NIM & I'm choosing to do CD install.. The Install method would be Upgrade installation. Is there anything special that I need to consider before... (5 Replies)
Discussion started by: kkeng808
5 Replies

5. AIX

Migrating RHEL 5 UNIX users to AIX

Hi, I'm able to migrate UNIX users/groups from Solaris to AIX (with same password using 13-char encrypted password from shadow file) but no luck with RHEL 5 to AIX. I see encrypted password in RHEL 5 is bit lengthier than 13-char. Is there any way to convert encrypted password such that same... (1 Reply)
Discussion started by: reddyr
1 Replies

6. Linux

Migrating RCS from HP-UX to Linux

Hello all, We would be migrating from HP-UX 11 to Red Hat Linux 5 shortly. On HP-UX we've been using RCS (Revision Control system). On RHEL I think there is an equivilant utility called Subversion..Is there a way to export the current contents from RCS in HP-UX and import it into Linux's... (2 Replies)
Discussion started by: luft
2 Replies

7. Linux

Migrating to new server

Hi I configured a full blown Suse Linux server with FTP (VSFTP) server (98 users), Samba as well as secure Ftp on Suse Linux 10 SP4. I need to transfer the whole system to a NEW server that I configured with Ver 11.4 What files need to be backed up and restored to the new server keeping the... (5 Replies)
Discussion started by: Tony.Marshall
5 Replies

8. Red Hat

Logged in users on a Linux server are counted twice

Scenario: 1. Log into a linux server interface as root. 2. Inititiate an SSH session with the server using Putty and a valid user account (e.g. fakeuser). 3. Log into TTY2 of the linux server interface using another valid user account (e.g. faketester). Issue: With these three login... (1 Reply)
Discussion started by: walterthered
1 Replies

9. Linux

Logged in users on a Linux server are counted twice

Scenario: Log into a linux server interface as root. Inititiate an SSH session with the server using Putty and a valid user account (e.g. fakeuser). Log into TTY2 of the linux server interface using another valid user account (e.g. faketester). Issue: With these three login sessions,... (8 Replies)
Discussion started by: walterthered
8 Replies
SYSUSERS.D(5)							    sysusers.d							     SYSUSERS.D(5)

NAME
sysusers.d - Declarative allocation of system users and groups SYNOPSIS
/etc/sysusers.d/*.conf /run/sysusers.d/*.conf /usr/lib/sysusers.d/*.conf DESCRIPTION
systemd-sysusers uses the files from sysusers.d directory to create system users and groups at package installation or boot time. This tool may be used to allocate system users and groups only, it is not useful for creating non-system (i.e. regular, "human") users and groups, as it accesses /etc/passwd and /etc/group directly, bypassing any more complex user databases, for example any database involving NIS or LDAP. CONFIGURATION DIRECTORIES AND PRECEDENCE
Each configuration file shall be named in the style of package.conf or package-part.conf. The second variant should be used when it is desirable to make it easy to override just this part of configuration. Files in /etc/sysusers.d override files with the same name in /usr/lib/sysusers.d and /run/sysusers.d. Files in /run/sysusers.d override files with the same name in /usr/lib/sysusers.d. Packages should install their configuration files in /usr/lib/sysusers.d. Files in /etc/sysusers.d are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied. All later entries for the same user and group names will be logged as warnings. If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/sysusers.d/ bearing the same filename. CONFIGURATION FILE FORMAT
The file format is one line per user or group containing name, ID, GECOS field description and home directory: #Type Name ID GECOS Home directory u httpd 440 "HTTP User" u authd /usr/bin/authd "Authorization user" g input - - m authd input u root 0 "Superuser" /root Empty lines and lines beginning with the "#" character are ignored, and may be used for commenting. Type The type consists of a single letter. The following line types are understood: u Create a system user and group of the specified name should they not exist yet. The user's primary group will be set to the group bearing the same name. The user's shell will be set to /sbin/nologin, the home directory to the specified home directory, or / if none is given. The account will be created disabled, so that logins are not allowed. g Create a system group of the specified name should it not exist yet. Note that u implicitly create a matching group. The group will be created with no password set. m Add a user to a group. If the user or group do not exist yet, they will be implicitly created. r Add a range of numeric UIDs/GIDs to the pool to allocate new UIDs and GIDs from. If no line of this type is specified, the range of UIDs/GIDs is set to some compiled-in default. Note that both UIDs and GIDs are allocated from the same pool, in order to ensure that users and groups of the same name are likely to carry the same numeric UID and GID. Name The name field specifies the user or group name. The specified name must consist only of the characters a-z, A-Z, 0-9, "_" and "-", except for the first character which must be one of a-z, A-Z or "_" (i.e. numbers and "-" are not permitted as first character). The user/group name must have at least one character, and at most 31. It is strongly recommended to pick user and group names that are unlikely to clash with normal users created by the administrator. A good scheme to guarantee this is by prefixing all system and group names with the underscore, and avoiding too generic names. For m lines, this field should contain the user name to add to a group. For lines of type r, this field should be set to "-". ID For u and g, the numeric 32-bit UID or GID of the user/group. Do not use IDs 65535 or 4294967295, as they have special placeholder meanings. Specify "-" for automatic UID/GID allocation for the user or group. Alternatively, specify an absolute path in the file system. In this case, the UID/GID is read from the path's owner/group. This is useful to create users whose UID/GID match the owners of pre-existing files (such as SUID or SGID binaries). The syntax "uid:gid" is also supported to allow creating user and group pairs with different numeric UID and GID values. The group with the indicated GID must get created explicitly before or it must already exist. For m lines, this field should contain the group name to add to a user to. For lines of type r, this field should be set to a UID/GID range in the format "FROM-TO", where both values are formatted as decimal ASCII numbers. Alternatively, a single UID/GID may be specified formatted as decimal ASCII numbers. GECOS A short, descriptive string for users to be created, enclosed in quotation marks. Note that this field may not contain colons. Only applies to lines of type u and should otherwise be left unset, or be set to "-". Home Directory The home directory for a new system user. If omitted, defaults to the root directory. It is recommended to not unnecessarily specify home directories for system users, unless software strictly requires one to be set. Only applies to lines of type u and should otherwise be left unset, or be set to "-". IDEMPOTENCE
Note that systemd-sysusers will do nothing if the specified users or groups already exist, so normally, there is no reason to override sysusers.d vendor configuration, except to block certain users or groups from being created. SEE ALSO
systemd(1), systemd-sysusers(8) systemd 237 SYSUSERS.D(5)
All times are GMT -4. The time now is 04:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy