06-23-2005
reset on a lot of systems will put your terminal back to some reasonable setting.
10 More Discussions You Might Find Interesting
1. Programming
Hi , I am working on SCO Unix who needs to know some basics concepts about how to write a program that will capture the input , output of one terminal to another ie whatever is being typed as input or echoed as output to terminal say tty02 shall be automatically be falshed to another terminal say... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
Am new to the forum and hope this post meets the requirements.
This post will be rather lengtly but needs to be to explain the problem.
I have two computers running Windows 2000 Pro. I travel for a living and use a terminal emulation program called STEP to connect to our Unix... (2 Replies)
Discussion started by: skids
2 Replies
3. BSD
Hi !
As everyone, i installed my system and started "personalizing" it. One of the adjustments was creating an alias in /etc/profile fo ls, so when I type ls it is running ls -G so i can see a colored output. Everything is ok, but after I configured my system to start in X by default (kdm as... (2 Replies)
Discussion started by: Sergiu-IT
2 Replies
4. SCO
Question from a newbie:
We are running SCO Unix, and are using Century Software Windows Terminal Emulation “Term for Windows” for Win95 v6.3.9b.
It used to work fine when we had Win98 on our machines, but now we are updating them with Win2000/XP.
This WinTerm works fine on some machines, which... (9 Replies)
Discussion started by: fasal
9 Replies
5. UNIX for Dummies Questions & Answers
HI , I am little confused about differences between Telnet and Terminal Emulation? (1 Reply)
Discussion started by: nixhead
1 Replies
6. AIX
Greetings. We share one AIX server with about 100 users over 4 hub sites via Procomm Plus. Users dvelop bad habits and exit straight out of the terminal window vice correctly logging out of their application session on the server. Sometimes we have to go into the server and terminate their session... (0 Replies)
Discussion started by: pconfig
0 Replies
7. Solaris
I am having issues with installation of Sterling-Gentran:Server for UNIX 6.1. The issue within the secadmin setup. I can get into the Security Admin Setup Screens and can navigate within but cannot reply to a popup screen (the software is asking me to confirm "YES" or "NO" and none of the keys on... (6 Replies)
Discussion started by: oakbob817
6 Replies
8. Programming
have the following lines in .bash_profile. "ln-s /dev/ttyp0 /dev/lpw10" and ln -s /dev/ttyp0 /dev/lpc10"
this allows a terminal emulation running on xp to print locally.
I would like to capture the print file and store the output in a directory.
Any ideas as to how to capture the print output?... (2 Replies)
Discussion started by: petercp
2 Replies
9. UNIX for Dummies Questions & Answers
I use a program called TinyTerm to access our AIX machine. It works fine except for when I rlogin into our SCO unix server. Backspace doesn't delete, ctrl-c doesn't work (delete key does same thing), and the most annoying thing is vi acts very wierd. I have to press the down arrow like 3 times to... (11 Replies)
Discussion started by: herot
11 Replies
10. UNIX for Dummies Questions & Answers
I am using Terminal on an OSX system to access and edit crontab files on a 'headless' Solaris 11 server. Crontab -e on OSX invokes vi as the editor, which is fine, but I am getting unexpected characters on keystrokes and have to abort the edit. If this is an emulation issue, would someone please... (1 Reply)
Discussion started by: SmokeyJoe
1 Replies
LEARN ABOUT DEBIAN
urxvtd
urxvt(1) RXVT-UNICODE urxvt(1)
NAME
urxvtd - urxvt terminal daemon
SYNOPSIS
urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork] [-m|--mlock]
urxvtd -q -o -f # for .xsession use
DESCRIPTION
This manpage describes the urxvtd daemon, which is the same vt102 terminal emulator as urxvt, but runs as a daemon that can open multiple
terminal windows within the same process.
You can run it from your X startup scripts, for example, although it is not dependent on a working DISPLAY and, in fact, can open windows
on multiple X displays on the same time.
Advantages of running a urxvt daemon include faster creation time for terminal windows and a lot of saved memory.
The disadvantage is a possible impact on stability - if the main program crashes, all processes in the terminal windows are terminated. For
example, as there is no way to cleanly react to abnormal connection closes, "xkill" and server resets/restarts will kill the urxvtd
instance including all windows it has opened.
OPTIONS
urxvtd currently understands a few options only. Bundling of options is not yet supported.
-q, --quiet
Normally, urxvtd outputs the message "rxvt-unicode daemon listening on <path>" after binding to its control socket. This option will
suppress this message (errors and warnings will still be logged).
-o, --opendisplay
This forces urxvtd to open a connection to the current $DISPLAY and keep it open.
This is useful if you want to bind an instance of urxvtd to the lifetime of a specific display/server. If the server does a reset,
urxvtd will be killed automatically.
-f, --fork
This makes urxvtd fork after it has bound itself to its control socket.
-m, --mlock
This makes urxvtd call mlockall(2) on itself. This locks urxvtd in RAM and prevents it from being swapped out to disk, at the cost of
consuming a lot more memory on most operating systems.
Note: In order to use this feature, your system administrator must have set your user's RLIMIT_MEMLOCK to a size greater than or equal
to the size of the urxvtd binary (or to unlimited). See /etc/security/limits.conf.
Note 2: There is a known bug in glibc (possibly fixed in 2.8 and later versions) where calloc returns non-zeroed memory when mlockall
is in effect. If you experience crashes or other odd behaviour while using --mlock, try it without it.
EXAMPLES
This is a useful invocation of urxvtd in a .xsession-style script:
urxvtd -q -f -o
This waits till the control socket is available, opens the current display and forks into the background. When you log-out, the server is
reset and urxvtd is killed.
ENVIRONMENT
RXVT_SOCKET
Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to create a listening socket and to contact the urxvtd, respectively.
If the variable is missing then $HOME/.urxvt/urxvtd-<nodename> is used.
DISPLAY
Only used when the "--opendisplay" option is specified. Must contain a valid X display name.
SEE ALSO
urxvt(7), urxvtc(1)
9.15 2012-01-21 urxvt(1)