Shared Home directory between Unix servers


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Shared Home directory between Unix servers
# 1  
Old 02-22-2008
PHP Shared Home directory between Unix servers

Hi
Im working in an environment where 2 production and 2 testing unix servers are used.. All these servers share the same home directory..
how is it done
where would the home directory be located
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Use programs in shared folder except ones in my home dir

I am using a cluster where all the programs are located in a shared folder (I can only read but not modify anything in this folder). The path of the share folder is in my .bashrc file (and thus also in my $PATH - first position): source /home/shared/bashrc But some of the programs are... (5 Replies)
Discussion started by: beca123456
5 Replies

2. Shell Programming and Scripting

Use programs in shared folder except ones in my home dir

(0 Replies)
Discussion started by: beca123456
0 Replies

3. Shell Programming and Scripting

Search in Unix home directory

I have many views in my Linux home dir under different folders mentioned below. Home 1. CCVIEWS 2. views 3. Development 4. testproject : : etc. Now i want to list all the clearcase views in my linux dir in below format to work on other script. 1) user_test_Work1.vws ... (4 Replies)
Discussion started by: saku
4 Replies

4. UNIX for Dummies Questions & Answers

Unix set home directory

Hi I've just made a directory, what command do I use to now make it the base directory? Thanks!!!!!!!!!!!!!!! (1 Reply)
Discussion started by: beckywatson
1 Replies

5. UNIX for Dummies Questions & Answers

Copying files from unix servers to other locations e.g. C directory

Hi, I am just wondering is it possible to move or copy a file from a UNIX server to a different location e.g. the C drive on a computer? I have used the cp command to move files to different locations on unix servers but it would be handy to move a file to my C drive. I am currently... (3 Replies)
Discussion started by: crunchie
3 Replies

6. AIX

CD Rom shared for many AIX servers.

Guy's I have more than 20 servers available in different locations and I want to configure CD Rom as NFS between these servers to be sharedCan any one explain the configuration how can NFS or share CD rom between more than 20 servers available in different locationsto be used in one time from all... (5 Replies)
Discussion started by: Mr.AIX
5 Replies

7. UNIX for Advanced & Expert Users

Shared hosting, how to install programs and libraries in your home folder

Hi all I hope I am posting in the right section. If not please excuse me and redirect me to the right section. Here is my problem: I am using a shared hosting plan at Godady. I have shell access and of course my own folder. I would like to be able to install programs in my own folder... (4 Replies)
Discussion started by: PiniFarini
4 Replies

8. UNIX for Dummies Questions & Answers

home directory & group in UNIX question

folks; I'm going to use LDAP on Solaris 10 to authenticate users, i have 3 questions, i'm hoping it can be possible: 1. when users login for the first time, Is there a way to auto create a home directory like "/home/"user_name" so we don't have to a create a home directory for every single... (3 Replies)
Discussion started by: Katkota
3 Replies

9. UNIX for Dummies Questions & Answers

copy file from UNIX to shared directory

Hi, I want to copy a file from unix machine to a shared windows directory. i tried using the ftp command but i was able to transfer the file only to my local directory. Is there any way we can transfer/copy the files from unix to windows shared directory.......... Please help. Thanks (5 Replies)
Discussion started by: sireesha15
5 Replies
Login or Register to Ask a Question
nisping(1M)															       nisping(1M)

NAME
nisping - send ping to NIS+ servers SYNOPSIS
/usr/lib/nis/nisping [-uf] [-H hostname] [-r | directory] /usr/lib/nis/nisping -C [-a] [-H hostname] [directory] In the first line, the nisping command sends a ``ping'' to all replicas of an NIS+ directory. Once a replica receives a ping, it will check with the master server for the directory to get updates. Prior to pinging the replicas, this command attempts to determine the last update "seen" by a replica and the last update logged by the master. If these two timestamps are the same, the ping is not sent. The -f (force) option will override this feature. Under normal circumstances, NIS+ replica servers get the new information from the master NIS+ server within a short time. Therefore, there should not be any need to use nisping. In the second line, the nisping -C command sends a checkpoint request to the servers. If no directory is specified, the home domain, as returned by nisdefaults(1), is checkpointed. If all directories, served by a given server, have to be checkpointed, then use the -a option. On receiving a checkpoint request, the servers would commit all the updates for the given directory from the table log files to the data- base files. This command, if sent to the master server, will also send updates to the replicas if they are out of date. This option is needed because the database log files for NIS+ are not automatically checkpointed. nisping should be used at frequent intervals (such as once a day) to checkpoint the NIS+ database log files. This command can be added to the crontab(1) file. If the database log files are not checkpointed, their sizes will continue to grow. If the server specified by the -H option does not serve the directory, then no ping is sent. Per-server and per-directory access restrictions may apply; see nisopaccess(1). nisping uses NIS_CPTIME and NIS_PING (resync (ping) of replicas), or NIS_CHECKPOINT (for checkpoint). Since the NIS_PING operation does not return a status, the nisping command is typically unable to indicate success or failure for resyncs. -a Checkpoint all directories on the server. -C Send a request to checkpoint, rather than a ping, to each server. The servers schedule to commit all the transactions to stable storage. -H hostname Only the host hostname is sent the ping, checked for an update time, or checkpointed. -f Force a ping, even though the timestamps indicate there is no reason to do so. This option is useful for debugging. -r This option can be used to update or get status about the root object from the root servers, especially when new root replicas are added or deleted from the list. If used without -u option, -r will send a ping request to the servers serving the root domain. When the replicas receive a ping, they will update their root object if needed. The -r option can be used with all other options except with the -C option; the root object need not be checkpointed. -u Display the time of the last update; no servers are sent a ping. -1 No servers were contacted, or the server specified by the -H switch could not be contacted. 0 Success. 1 Some, but not all, servers were successfully contacted. Example 1: Using nisping This example pings all replicas of the default domain: example% nisping Note that this example will not ping the org_dir and groups_dir subdirectories within this domain. This example pings the server example which is a replica of the org_dir.foo.com. directory: example% nisping -H example org_dir.foo.com. This example checkpoints all servers of the org_dir.bar.com. directory. example% nisping -C org_dir.bar.com. NIS_PATH If this variable is set, and the NIS+ directory name is not fully qualified, each directory specified will be searched until the directory is found. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ crontab(1), nisdefaults(1), nisopaccess(1), nislog(1M), nisfiles(4), attributes(5) NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. 12 Dec 2001 nisping(1M)