03-31-2009
Quote:
We believe this is an X Server issue.
Yes indeed, and who is the Xserver in this case?
What makes you think its th HP side that is causing the issue? dtterm is native in HP..., not in RH...
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
we have an hp-ux and a user requested me if i can password protect the dtterm. i know that this is possible but can you give me some hints in making this happen?
thanks :cool: (2 Replies)
Discussion started by: inquirer
2 Replies
2. UNIX for Dummies Questions & Answers
Working of a Aix 4.3 (using ksh)
Have started dtlogin daemon .
< root 26376 1 0 14:07:19 - 0:08 ./dtlogin -daemon >
Have set dtconfig -e
< The CDE environment is Already set as the default User Interface. >
Have executed " export DISPLAY=10.1.187.86:0.0
Once all this is... (4 Replies)
Discussion started by: buRst
4 Replies
3. Red Hat
Hello,
We are having a problem with running dtterm off a RHEL server. Logging into an HP-UX server from a RHEL 5.1 desktop, setting DISPLAY and running dtterm, the caps lock does not work. We have been playing with xmodmap & stty but to no avail.
Any help appreciated.
mgb (1 Reply)
Discussion started by: mgb
1 Replies
4. UNIX for Advanced & Expert Users
Hello,
Not sure if this is the right place to post it but..
I have a requirement to set Caps lock and/or Num lock on and off via a Cron job.
Now I have working scripts that do the job, but as soon as X starts up the jobs no longer run (well they appear to, but Caps lock and Num lock do not... (0 Replies)
Discussion started by: autotuner
0 Replies
5. Red Hat
Hello all,
If anyone has time, I have a few questions:
How do I do the following in Linux. We are using Red Hat and Oracle Enterprise Linux, which is based on Red Hat too.
1. How to lock the account after a few (like 3) invalid password attempts?
2. How do you lock a screen after 30... (1 Reply)
Discussion started by: nstarz
1 Replies
6. Shell Programming and Scripting
I'm trying to write a shell script that runs periodically and if I'm not at the keyboard, it should do one thing, but if I am at the keyboard, it should do another thing. Therefore I've decided that it would be good if I could press down the CTRL key, (or some other key) and have the shell script... (8 Replies)
Discussion started by: Ilja
8 Replies
7. UNIX for Advanced & Expert Users
Hi all,
I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...).
I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message.
Is there any way to simply get a return code... (3 Replies)
Discussion started by: Dedalus
3 Replies
8. UNIX for Dummies Questions & Answers
hi all
this s quite a foolish problem. I seem to hav pressed some keys s.t in unix, my letters are comin in caps and with caps lock on, i am getting lowercase letters. :o
Pls help.
Also is there any reference or manual where i can check in case such problems arrise?
thanx in advance
curiosity (4 Replies)
Discussion started by: curiosity
4 Replies
9. Shell Programming and Scripting
With use of sed/awk, how can I print all possible combinations of a word with caps/non-caps.
Eg
Applying operation on "cap" should generate output as follows.
cap
CAP
Cap
cAp
caP
CAp
cAP
CaP (12 Replies)
Discussion started by: anil510
12 Replies
lockd(8c) lockd(8c)
Name
lockd - network lock daemon
Syntax
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]
Description
The 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 system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, 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 daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.
Options
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.
-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.
See Also
fcntl(2), lockf(3), signal(3), statd(8c)
lockd(8c)