Sponsored Content
Full Discussion: lost home directory
Operating Systems Solaris lost home directory Post 302272190 by Msororaji on Tuesday 30th of December 2008 12:42:43 AM
Old 12-30-2008
Thanks for your response guys


The response for df -k /home is below
Quote:
root@PRD#
root@PRD#df -k /home
Filesystem kbytes used avail capacity Mounted on
auto_home 0 0 0 0% /home
root@PRD#

however I realize when the home directories were visible command df -k /home would show it mounted on device /dev/md/dsk/d30 which has the root filesystem .

I believe the person who created the users picked /home as the home directory for the users he created




NIS/LDAP or similar name services are not in use

in /etc/nsswitch.conf
automount: files

I'm not sure where the backing filesystem for the home directories is local or remote but I have a backup of the root filesystem
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

c++ home directory??

when i compile *.cpp files the compiler didn't find the non standart includes.If i have to put the full path of the includet files where shall i begin from root dirctory or i heve to put includet files in cpp home directory??? can i compile java files in unix(linux mandrake 7) if yes haw... (3 Replies)
Discussion started by: user666
3 Replies

2. UNIX for Dummies Questions & Answers

lost+found directory

what is the directory "lost+found" and how is it used? (2 Replies)
Discussion started by: Ben070371
2 Replies

3. UNIX for Dummies Questions & Answers

cd into home directory ~

I'm trying to cd into a home directory with cd ~username_here and I'm getting the following error: ~username_here: does not exist The directory exists and I can directly go to it via cd /export/home/username_here without any problems. Any suggestions? (4 Replies)
Discussion started by: here2learn
4 Replies

4. Solaris

Deleted Lost+Found directory

If you delete your lost & found directory, how do you get it back, just do a mkdir? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

5. Solaris

Deletion of Data from Lost+Found Directory

Hie I am running a sun solaris server of about 300 gigabytes disk capacity. The problem is that the machine has been having problems over the past year and at times the machine would just freeze or hang and had to be re-booted. Consequently there are too many entries in the lost+found... (1 Reply)
Discussion started by: Ranganai
1 Replies

6. UNIX for Dummies Questions & Answers

lost /home/directory for users

I'm using HPUX 11i. The other day a user logon to the workstation and was not able to find the /home/directory (tom is the directory) I login myself and it is the same thing. The home directory is on the server, so I was thinking of using sam to map it again. does anyone know how to do it... (5 Replies)
Discussion started by: blizzgamer
5 Replies

7. Shell Programming and Scripting

home directory

hello i want shell script. as root , i want to untar specific.tar.gz to all home user directory and after untar , there is 1.txt 2.txt ~~ 26.txt in/public_html/test1/ i want randomly selected 6 text files in 1.txt 2.txt ~26.txt to be renamed newword1.word , newword2.word , ~~... (8 Replies)
Discussion started by: topic32428285
8 Replies

8. Solaris

Restricting SFTP user to a defined directory and home directory

Hi, I've created solaris user which has both FTP and SFTP Access. Using the "ftpaccess" configuration file options "guest-root" and "restricted-uid", i can restrict the user to a specific directory. But I'm unable to restrict the user when the user is logged in using SFTP. The aim is to... (1 Reply)
Discussion started by: sftpuser
1 Replies

9. Solaris

SunOS confusing root directory and user home directory

Hello, I've just started using a Solaris machine with SunOS 5.10. After the machine is turned on, I open a Console window and at the prompt, if I execute a pwd command, it tells me I'm at my home directory (someone configured "myuser" as default user after init). ... (2 Replies)
Discussion started by: egyassun
2 Replies
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)
All times are GMT -4. The time now is 02:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy