Sponsored Content
Operating Systems Solaris rootsh on Solaris 10 is not sourcing root's .profile Post 302374895 by kungfusnwbrdr on Wednesday 25th of November 2009 07:56:15 PM
Old 11-25-2009
rootsh on Solaris 10 is not sourcing root's .profile

I'm attempting to setup rootsh on Solaris 10 to log the activity of users who require root access. However it does not appear to be sourcing root's .profile file even when run with the '-i' option. I was wondering if anybody else has run into this and might have a solution.

Thank you.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SunOS - root's .profile

There is no .profile file for the root user. It should reside in "/". Can I just copy a .profile file into "/"? (3 Replies)
Discussion started by: xadamz23
3 Replies

2. Solaris

.profile for root ?

Hi friends, On a Solaris system is the .profile executed for the user root also as it is for any normal user ? if i have to change the PATH variable can i add it to the .profile? and by default ther .profile is not found in the / directory. i can see it in /etc as /etc/profile. Should i... (1 Reply)
Discussion started by: sveera
1 Replies

3. UNIX for Dummies Questions & Answers

How to change root's .profile settings

As a regular (non-root) user on Unix servers I'm accustomed to changing my .profile file to set paths that I frequently use, etc. I am trying to learn unix and set up a test server running SunOS 5.8. When I login as root I don't see a .profile file that belongs to root wherein I could change the... (1 Reply)
Discussion started by: FredSmith
1 Replies

4. Solaris

trying to add .profile for root

I am trying to add a .profile for root I cd to / do vi .profile and get /var/tmp/ExGXaaqa Read only file system... What does this mean? (4 Replies)
Discussion started by: liven
4 Replies

5. AIX

Ho to copy root profile?

Does anybody know how to copy/mirror root profile in AIX 5.2? (1 Reply)
Discussion started by: fraydey
1 Replies

6. AIX

aix 6.1 root .profile not found

hello all i just installed my 1rst 6.1 machine and it's working fine but i can't find the root .profile ????? can any one help BEst Regards (1 Reply)
Discussion started by: islam.said
1 Replies

7. Shell Programming and Scripting

sourcing .profile for other users

Hi Team, Thank you for your time. i have a situation where the user IDs of the applicatio users have been locked down to Read only. Hence I am writing a script to invoke their old .profile every time they login. My problem is : when i run . $userpath/.profile from within the ksh script... (9 Replies)
Discussion started by: anitha111
9 Replies

8. UNIX for Dummies Questions & Answers

switch user (su) not sourcing the profile

Usually in solaris/Linux servers , when you do an su - username (space before and after the hyphen) the user's .profile should get sourced. But in the below linux machine it is not. As you see below ORACLE_HOME variable is not being set. # uname -a Linux revaltb214 2.6.18-238.el5 #1 SMP Sun... (7 Replies)
Discussion started by: John K
7 Replies

9. Shell Programming and Scripting

Sourcing as root automatically

Hey everyone! I have my .bash_profile file which is read automatically when I launch Terminal therefore I can run my own functions. BUT. When I do: sudo -s sudo su sudo su - No matter what I do, I can't get the .bash_profile file to be sourced automatically so I end up having to run... (2 Replies)
Discussion started by: dasx
2 Replies

10. UNIX for Advanced & Expert Users

Dot sourcing differences in ksh, AIX vs Linux vs Solaris

Why does dot sourcing of ksh functions behave so differently between AIX, Solaris, and Linux? How can I make Linux behave the way I want in the test I show below? I have a library of interdependent functions I have developed and use in ksh in AIX. They also run in Solaris. Now I am migrating... (9 Replies)
Discussion started by: charles_n_may
9 Replies
HOSTS.EQUIV(5)                                               Linux Programmer's Manual                                              HOSTS.EQUIV(5)

NAME
hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system DESCRIPTION
The file /etc/hosts.equiv allows or denies hosts and users to use the r-commands (e.g., rlogin, rsh, or rcp) without supplying a password. The file uses the following format: +|[-]hostname|+@netgroup|-@netgroup [+|[-]username|+@netgroup|-@netgroup] The hostname is the name of a host which is logically equivalent to the local host. Users logged into that host are allowed to access like-named user accounts on the local host without supplying a password. The hostname may be (optionally) preceded by a plus (+) sign. If the plus sign is used alone, it allows any host to access your system. You can explicitly deny access to a host by preceding the hostname by a minus (-) sign. Users from that host must always supply additional credentials, including possibly a password. For security reasons you should always use the FQDN of the hostname and not the short hostname. The username entry grants a specific user access to all user accounts (except root) without supplying a password. That means the user is NOT restricted to like-named accounts. The username may be (optionally) preceded by a plus (+) sign. You can also explicitly deny access to a specific user by preceding the username with a minus (-) sign. This says that the user is not trusted no matter what other entries for that host exist. Netgroups can be specified by preceding the netgroup by an @ sign. Be extremely careful when using the plus (+) sign. A simple typographical error could result in a standalone plus sign. A standalone plus sign is a wildcard character that means "any host"! FILES
/etc/hosts.equiv NOTES
Some systems will honor the contents of this file only when it has owner root and no write permission for anybody else. Some exceptionally paranoid systems even require that there be no other hard links to the file. Modern systems use the Pluggable Authentication Modules library (PAM). With PAM a standalone plus sign is considered a wildcard character which means "any host" only when the word promiscuous is added to the auth component line in your PAM file for the particular service (e.g., rlogin). EXAMPLE
Below are some example /etc/host.equiv or ~/.rhosts files. Allow any user to log in from any host: + Allow any user from host with a matching local account to log in: host Note: the use of +host is never a valid syntax, including attempting to specify that any user from the host is allowed. Allow any user from host to log in: host + Note: this is distinct from the previous example since it does not require a matching local account. Allow user from host to log in as any non-root user: host user Allow all users with matching local accounts from host to log in except for baduser: host -baduser host Deny all users from host: -host Note: the use of -host -user is never a valid syntax, including attempting to specify that a particular user from the host is not trusted. Allow all users with matching local accounts on all hosts in a netgroup: +@netgroup Disallow all users on all hosts in a netgroup: -@netgroup Allow all users in a netgroup to log in from host as any non-root user: host +@netgroup Allow all users with matching local accounts on all hosts in a netgroup except baduser: +@netgroup -baduser +@netgroup Note: the deny statements must always precede the allow statements because the file is processed sequentially until the first matching rule is found. SEE ALSO
rhosts(5), rlogind(8), rshd(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-07-23 HOSTS.EQUIV(5)
All times are GMT -4. The time now is 10:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy