dwatts@ki.UUCP (Dan Watts) (11/01/90)
I ran into a slight problem getting a UUCP account configured on my
RS/6000 and was wondering if anyone else has had similar problems.
The first problem I ran into, was that smit wouldn't let me designate
/usr/lib/uucp/uucico as the initial program. Smit would give me an
error that the choice was invalid. I ended up having to select /bin/ksh,
exit smit, and then edit /etc/passwd and change the /bin/ksh to what
I wanted. Renetering smit showed that the change was affective.
The next problem I found was that when a uucp account logs in, I get
/etc/motd displayed on the screen! Is there anyway to disable this
(other than renaming motd which is what I've done for the time being)?
On a related note, is there a way to create a new user with a group
other than the default? When I create a user and then change the group
id to what I want, I then have to manually fix the home directory that
smit created and all the files in it to have the correct group id.
--
#####################################################################
# CompuServe: >INTERNET:uunet.UU.NET!ki!dwatts Dan Watts #
# UUCP : ...!{uunet | wgc386}!ki!dwatts Ki Research, Inc. #
############### New Dimensions In Network Connectivity ##############marc@ibmpa.awdpa.ibm.com (Marc Pawliger) (11/02/90)
In article <875@ki.UUCP>, dwatts@ki.UUCP (Dan Watts) writes: |> I ran into a slight problem getting a UUCP account configured on my |> RS/6000 and was wondering if anyone else has had similar problems. |> The first problem I ran into, was that smit wouldn't let me designate |> /usr/lib/uucp/uucico as the initial program. Smit would give me an |> error that the choice was invalid. I ended up having to select /bin/ksh, |> exit smit, and then edit /etc/passwd and change the /bin/ksh to what |> I wanted. Renetering smit showed that the change was affective. This is because there is a limited number of programs that can be selected as the login shell, so that you couldn't make, say, /bin/logout be the login shell by mistake. There is a file that lists the valid choices in SMIT (and mkuser, which SMIT invokes under the covers) for the login shell. That file is /etc/security/login.cfg. Just add /usr/lib/uucp/ uucico to the 'usw' stanza in the file and you can now select uucico as the login shell for a user. These are my opinions, not IBM's etc etc etc +---Marc Pawliger---IBM Advanced Workstations Division---Palo Alto, CA---+ | Internet: marc@ibminet.awdpa.ibm.com VNET: MARCP at AUSVM6 | | UUCP: uunet!ibmsupt!ibmpa!marc Phone: (415) 855-3493 | +------IBMnet: marc@ibmpa.awdpa.ibm.com------IBM T/L: 465-3493--------+
steve@qe2.awdpa.ibm.com (Steve DeJarnett) (11/02/90)
In article <875@ki.UUCP> dwatts@ki.UUCP (Dan Watts) writes: >I ran into a slight problem getting a UUCP account configured on my >RS/6000 and was wondering if anyone else has had similar problems. >The first problem I ran into, was that smit wouldn't let me designate >/usr/lib/uucp/uucico as the initial program. Smit would give me an >error that the choice was invalid. I ended up having to select /bin/ksh, >exit smit, and then edit /etc/passwd and change the /bin/ksh to what >I wanted. Renetering smit showed that the change was affective. Edit the file /etc/security/login.cfg and look near the bottom of the file. There is a "usw" stanza that specifies the shells that are allowable for user's login shells (along the lines of the /etc/shells file in BSD (and probably SysV as well)). Add /usr/lib/uucp/uucico to that line and SMIT should be happy about letting you add a user with uucico as their shell. >The next problem I found was that when a uucp account logs in, I get >/etc/motd displayed on the screen! Is there anyway to disable this >(other than renaming motd which is what I've done for the time being)? Create a file called .hushlogin in the user's home directory. It doesn't matter what (if anything) is in it. It's usually just a file that was "touched" (i.e. 0-length). >On a related note, is there a way to create a new user with a group >other than the default? When I create a user and then change the group >id to what I want, I then have to manually fix the home directory that >smit created and all the files in it to have the correct group id. In the SMIT "Create User" screen, specify the primary group name. Thus, if you wanted to add a user whose primary group was "sysadmin", you would specify "sysadmin" as the user's primary group. After doing this, everything seemed to be owned by the correct user and have the correct group. Are you seeing something different?? (I am running on a system that's at a level beyond GOLD, so this may be a bug that has since been fixed). ># CompuServe: >INTERNET:uunet.UU.NET!ki!dwatts Dan Watts # Hope that helps. Steve DeJarnett Internet: steve@ibminet.awdpa.ibm.com IBM AWD Palo Alto UUCP: uunet!ibminet.awdpa.ibm.com!steve (415) 855-3510 IBM VNET: dejarnet at ausvmq These opinions are my own. I doubt IBM wants them.......