11-02-2018
Hi Stellaman;
The group ID's are not so much of a problem - however it is best practice to keep them aligned as some users may depend on group permissions for access to files/programs.
If you check the /etc/group file on each of the system, you should be able to bring both accounts into alignment. This can be done in the same manner that you aligned the user ID's, but you should check the group memberships as unlike user ID's many users can be members of groups.
Regards
Gull04
7 More Discussions You Might Find Interesting
1. HP-UX
Im trying to simply share a directory on one unix server and mount that share on a different unix server.
There is no "share" command like on sun. What is the command to create a share on HP-UX? (2 Replies)
Discussion started by: bski
2 Replies
2. IP Networking
Sometimes you get the tiger...but sometimes he get you and this latest home network “project” of mine has gnawed on me pretty badly. Perhaps you can offer some technical help. It will be heartily appreciated.
I have a small home network initially comprising two computers running Windows... (1 Reply)
Discussion started by: Annatar
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
Im running 32-bit solaris on sparc. We have a NAS(Network attached drive), with its IP address, username and password.
I'd like to be able to mount it on the solaris machine, and unmount it.
The best possibility would be able to mount it simulataneously on 2 or more systems.
Please... (9 Replies)
Discussion started by: 0ktalmagik
9 Replies
4. Solaris
How to move home directory of NIS user from one system to another system in Solaris.
Thanks & Regards
Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory.
with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2
catadm-M1$ ssh... (3 Replies)
Discussion started by: rbalaj16
3 Replies
6. Solaris
Hi,
I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name
here is what i did :
On the machine holding the internal disk
in vfstab i added the line
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies
7. Solaris
Hi,
I am having some NFS directory consistency problems with the below setup on a local (192.) network:
1. Different permissions (chmod) for the same NFS dir are reflected on different clients.
2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
LEARN ABOUT XFREE86
gshadow
GSHADOW(5) File Formats and Conversions GSHADOW(5)
NAME
gshadow - shadowed group file
DESCRIPTION
/etc/gshadow contains the shadowed information for group accounts.
This file must not be readable by regular users if password security is to be maintained.
Each line of this file contains the following colon-separated fields:
group name
It must be a valid group name, which exist on the system.
encrypted password
Refer to crypt(3) for details on how this string is interpreted.
If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, users will not be able to use a
unix password to access the group (but group members do not need the password).
The password is used when a user who is not a member of the group wants to gain the permissions of this group (see newgrp(1)).
This field may be empty, in which case only the group members can gain the group permissions.
A password field which starts with an exclamation mark means that the password is locked. The remaining characters on the line
represent the password field before the password was locked.
This password supersedes any password specified in /etc/group.
administrators
It must be a comma-separated list of user names.
Administrators can change the password or the members of the group.
Administrators also have the same permissions as the members (see below).
members
It must be a comma-separated list of user names.
Members can access the group without being prompted for a password.
You should use the same list of users as in /etc/group.
FILES
/etc/group
Group account information.
/etc/gshadow
Secure group account information.
SEE ALSO
gpasswd(5), group(5), grpck(8), grpconv(8), newgrp(1).
shadow-utils 4.5 01/25/2018 GSHADOW(5)