Linux OS : Fedora 10 (No graphical mode)
Windows OS : XP and Windows Server NT
I am able to access from my windows to linux using following step
//fedora10 ip
username of admin and password
I am able to view the admin and shared printer of fedora 10.
When i try to enter in the admin... (0 Replies)
Hi
I am using red hat linux, In my folder a strange folder is created i.e. " -a " , folder name is preceded with hyphen. Now if i try to remove with rm -rf -1 , i am unable to do it.
Can anyone please let me know how to do it, & what this kind of folder means
Thanks
Sarbjit (3 Replies)
Hi,
I am using redhat linux 5.1 - 64bit,
using command
mount -t cifs //192.192.192.192/SW/Ex /192.192.192.192 -o username=test
I am getting below error.
mount: block device //192.192.192.192/SW/Ex is write-protected, mounting read-only
mount: cannot mount block device... (3 Replies)
Hello Gurus!!
Very recently i tried to mount a USB pen drive onto my solaris 10 (X4170 model) server. As i understand, in ideal scenarios it should get mounted automatically, but it did not happen. Neither anything is shown in "iostat -En" output or "rmformat -l" about the pen drive.
I also... (10 Replies)
Hi All,
One job in unix server will generate .csv files daily. I need to copy the latest of these .csv file from the unix server to the shared drive/folder in windows through unix script. My shared folder will look something like
W:\some folder(for example). Could any one of you please help... (3 Replies)
We would be migrating unix solaries to Linux redhat.
Basically source is unix and target is linux.
i would like to copy entire file system unix/source/* to target linux/souce/*
but target linux has only folder setup so what ever files copied need to be placed in the linux server with same... (8 Replies)
Hi,
I followed this procedure in order to mount in AIX a shared folder in windows server 2000.
https://www-304.ibm.com/support/docview.wss?uid=isg3T1012550
Ive tested the shared folder from other windows Server, and its fine.
What Ive do in AIX is:
Logon as root
Under /Home/spss/ I... (2 Replies)
Hi everyone,
have a good day to you.
I am trying to use NFS to share a folder between 2 linux systems.
Let's say the server which is sharing the folder is server A and the client which need to access this shared folder is server B.
In server B, i am having a Joe user which UID and GID is 500.... (1 Reply)
Discussion started by: michael_hoang
1 Replies
LEARN ABOUT OSF1
rpc.lockd
rpc.lockd(8) System Manager's Manual rpc.lockd(8)NAME
rpc.lockd, lockd - Network lock daemon
SYNOPSIS
/usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]
OPTIONS
The default behavior will create and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
socket per protocol will be created and bind to the passed IP address. Available only on TruCluster Server systems. This option starts the
clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly. Highly available NFS service is config-
ured by default and typically does not require intervention. If you do need to start the clusterwide lock daemon, use the CAA command,
caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual. Internal Use Only. Use this option only under the direction
of technical support personnel. Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period dura-
tion instead of the default value of 15 seconds. Internal Use Only. Causes the rpc.lockd daemon to use the variable timeout (in
seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.
DESCRIPTION
The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status monitor daemon, rpc.statd,
for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests. Client site lock daemons
are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests. If a client site's lock daemon
fails to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
locks and cannot reclaim them.
SEE ALSO
Commands: rpc.statd(8)
Functions: fcntl(2), signal(2), lockf(3)rpc.lockd(8)