01-29-2012
hi methyl,
i logged out of my system n logged back in.. its working fine now. I still dont noe wat was wrong in the first place.
It was definitely not a stuck shift key or a problematic keyboard.
Also wat do u mean by a terminal emulator? Sorry but am very new to all this.
Thanks for your reply.
Regards
Curiosity
9 More Discussions You Might Find Interesting
1. Red Hat
hi friends
i have a small problem,in my redhat enterprise linux system screen lock is not working
if i click screen lock no action takes place...
so is there any solution to fix this problem or any alternate method available please let me know....
waiting for replys.......
thanks... (2 Replies)
Discussion started by: madhusudankh
2 Replies
2. 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
3. HP-UX
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 (7 Replies)
Discussion started by: mgb
7 Replies
4. Solaris
Hi,
I amnot able to execute any svm command. it gives the below message and hangs:
# metadetach d50 d30
metadetach: waiting on /etc/lvm/lock
^Cmetadetach: Interrupt
# metaclear d50
metaclear: waiting on /etc/lvm/lock
^Cmetaclear: Interrupt
Please advice.
Regards,
Sagar. (4 Replies)
Discussion started by: sag71155
4 Replies
5. 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
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. 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
8. Red Hat
I'm having a weird problem with a RHEL6 workstation. When the screen lock is activated manually the system will lock and the screens will go blank. Once I try to unlock the system, the monitor will just flicker and won't respond. I tried the combination CTRL, ALT, Backspace and it did not work,... (4 Replies)
Discussion started by: goose25
4 Replies
9. UNIX for Advanced & Expert Users
Hi Team,
I have a requirement to access a shared resource from the user and interrupt context. What type of locking mechanism I have to use for this. Can any body give advice on this.
Thanks in advance.
-Shiva (4 Replies)
Discussion started by: shivakoteswarra
4 Replies
WRITE(1) BSD General Commands Manual WRITE(1)
NAME
write -- send a message to another user
SYNOPSIS
write user [tty]
DESCRIPTION
The write utility allows you to communicate with other users, by copying lines from your terminal to theirs.
When you run the write command, the user you are writing to gets a message of the form:
Message from yourname@yourhost on yourtty at hh:mm ...
Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run write as well.
When you are done, type an end-of-file or interrupt character. The other user will see the message 'EOF' indicating that the conversation is
over.
You can prevent people (other than the super-user) from writing to you with the mesg(1) command.
If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the termi-
nal name as the second operand to the write command. Alternatively, you can let write select one of the terminals - it will pick the one
with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the right
place.
The traditional protocol for writing to someone is that the string '-o', either at the end of a line or on a line by itself, means that it is
the other person's turn to talk. The string 'oo' means that the person believes the conversation to be over.
SEE ALSO
mesg(1), talk(1), wall(1), who(1)
HISTORY
A write command appeared in Version 1 AT&T UNIX.
BUGS
The sender's LC_CTYPE setting is used to determine which characters are safe to write to a terminal, not the receiver's (which write has no
way of knowing).
BSD February 13, 2012 BSD