03-16-2009
Re: How to start CDE for non root user on Solaris 10
CDE will not start unless your user has a home directory so if your user is to have a local home directory make it as follows:
# mkdir /export/home/<username>
# chown <username> /export/home/<username>
Then ensure that the user's passwd entry points to /export/home/<username> for their home directory.
Then test it by doing:
# su - <username>
$ pwd
Ensure the directory response is now the user's home directory.
CDE is also particular about being able to resolve the machine's hostname so make sure /etc/hosts is a link to /etc/inet/hosts, that /etc/inet/hosts is chmodded to 644 and contains a line that gives the hostname and its IP address. Confirm that the hostname in /etc/nodename matches the hostname in /etc/inet/hosts and if you are running Solaris 10 ensure that /etc/inet/ipnodes is a link to /etc/inet/hosts (why did Sun introduce yet another "hosts" file called ipnodes?)
HTH.
Tony Fuller
10 More Discussions You Might Find Interesting
1. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (1 Reply)
Discussion started by: Awadhesh
1 Replies
2. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies
3. AIX
Hello.
I want to know how to start CDE on AIX, to export the console under reflection.
What commands are necesary to run on AIX to start CDE and after start It export the console using Reflection X.
Someboy know how to do that.
Regards (1 Reply)
Discussion started by: hmoday
1 Replies
4. Solaris
Hi I have a doubt, here if a file does not have the write permissions to the root user my script is going to write the data into that file. when i executed the script as root user. Is it correct ... ? (4 Replies)
Discussion started by: Shreedhar Naik
4 Replies
5. HP-UX
Dear Forum,
I had this problem initially with HPUX 11.23, all users including root could not login via CDE or telnet. Then after some workarounds, it resolved by resetting root password via console login. After enabling back all users to login normally (via CDE or telnet), only root can not... (4 Replies)
Discussion started by: irda
4 Replies
6. Solaris
Please let me know how to setup a non-root user to be able to access a privileged port (<1024) on Solaris 8. I am currently running tomcat as "tomcat" user and I get the following error during to start up:
SEVERE: Error initializing endpoint
java.net.BindException: Permission denied<null>:443 (5 Replies)
Discussion started by: pingmeback
5 Replies
7. HP-UX
how can i start sam in TUI mode from a CDE session.
i'm using hp-ux 11iv3
i tried to start SAM from a terminal from CDE session but each time i try to start it System Managment Homepage starts , so i telneted to server from a pc to start sam in TUI mode is there any other way to set my SAM to... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
8. UNIX Desktop Questions & Answers
Hello,
Do you guys by any chance know what is the best (if any ) way to move CDE configuration from a SOLARIS 10 machine to HP-UX?
Just the config (actions, text files etc).
Thanks in advance! (0 Replies)
Discussion started by: binary0x01
0 Replies
9. Solaris
I am not able to get ftp working for Solaris 10 for root user. I am getting login failed error.
331 Password required for root.
Password:
530 Login incorrect.
Login failed.
Tried following things already.
1. SFTP works ok, still would like to know why FTP is not working (curious).
2.... (5 Replies)
Discussion started by: webkid
5 Replies
10. Solaris
Welcome to all.
Have an issue and looking for help so hope someone is able to give me some clues.
I prepared some shell scripts with coloured output to help other guys to have more automated task. Not sure if I did this but now whenever I use 'ls' command for root user every output in... (29 Replies)
Discussion started by: TiedCone
29 Replies
LEARN ABOUT OSF1
hosts.equiv
hosts.equiv(4) Kernel Interfaces Manual hosts.equiv(4)
NAME
hosts.equiv - A file containing the names of remote systems and users that can execute commands on the local system
SYNOPSIS
/etc/hosts.equiv
DESCRIPTION
The /etc/hosts.equiv file and the .rhosts file in a user's home directory contain the names of remote hosts and users that are equivalent
to the local host or user. An equivalent host or user is allowed to access a local nonsuperuser account with the rsh command or rcp com-
mand, or to log in to such an account without having to supply a password.
The /etc/hosts.equiv file specifies equivalence for an entire system, while a user's .rhosts file specifies equivalence between that user
and remote users. The local user and the target system exist in the same area as the hosts.equiv file. The .rhosts file must be owned by
the user in whose home directory the file is located, or by the superuser. It cannot be a symbolic link.
Each line, or entry, in hosts.equiv or .rhosts may consist of the following: A blank line. A comment (begins with a #). A host name (a
string of any printable characters except newline, #, or white space). In addition, an NIS netgroup can be specified in place of the host
name. A host name followed by white space and a user name. In addition, an NIS netgroup can be specified in place of the host name, user
name, or both. A single plus (+) character. This means any host and user. The keyword NO_PLUS. This keyword disallows the use of the plus
character (+) to match any host or user on a system-wide basis. By default, the line containing this keyword is a comment. Remove the com-
ment character to disallow the use of the plus character.
Entries in the hosts.equiv file are either positive or negative. Positive entries allow access; negative entries deny access. The following
entries are positive: host name user name +@netgroup
In addition, the plus sign (+) can be used in place of the host name or user name. In place of the host name, it means any remote host. In
place of the user name, it means any user.
The following entries are negative: -host name -user name -@netgroup
To be allowed access or denied access, a user's remote host name and user name must match an entry in hosts.equiv or .rhosts. The
hosts.equiv file is searched first; if a match is found, the search ends. Therefore, the order in which the positive and negative entries
appear is important. If a match is not found, .rhosts is searched if it exists in the user's home directory.
A host name or user name can match an entry in hosts.equiv in one of the following ways: The official host name (not an alias) of the
remote host matches a host name in hosts.equiv. The remote user name matches a user name in hosts.equiv. If a user name parameter is
included in the hosts.equiv file, this means that the remote user is a trusted user and is allowed to rlogin to any local user account
without being prompted for a password. Otherwise, if the user name parameter is not specified in the hosts.equiv file, the name of the
remote user must match that of the local user. If the remote user name does not match a user name in hosts.equiv, the remote user name
matches the local user name.
CAUTIONS
For security purposes, the files /etc/hosts.equiv and .rhosts should exist and be readable and writable only by the owner, even if they are
empty.
EXAMPLES
The following are sample entries in an /etc/hosts.equiv file: # Allows access to users on host1 and host2 that have accounts on this host:
host1 host2 # Allows access to user johnson on host1 to any local user: host1 johnson # Allows access to all users on systems specified in
netgroup chicago +@chicago # Denies access to users specified in netgroup finance on host5 host5 -@finance # Allows access to all users on
all systems except root + -root
RELATED INFORMATION
Commands: rcp(1), rlogin(1), rsh(1)
Functions: ruserok(3).
Files: netgroup(4)
Daemons: rlogind(8), rshd(8) delim off
hosts.equiv(4)