05-21-2002
Terminal windows getting killed
Hi!!,
I am on HP UX- 11. We have just configured a new server. But facing a strange problem now. Occasionally our terminal windows get killed. any ideas about the cause??
Could someone tell me what to look for?? any particular logs?? or is it bcoz of too many processes ( ~ 70 -80 ) being run by the same user??
Thanks in advance...
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
hey all, i got a q
my computer at home runs Mac OS X so i use the terminal, and the computer(s) at school run Windows 98 (yuck) and i wanna know if there is a program for win 98 that is similar to terminal. and if possible, if they are compatible. (4 Replies)
Discussion started by: Pyrohotdog
4 Replies
2. UNIX for Dummies Questions & Answers
I'm brand spankin new to unix. What software would or could I use to reproduce what windows terminal server and citrix metaframe accomplish? To explain that, how do I create a server-based graphical desktop that can be accessed from a dumb terminal? Specificity is appreciated because I'm clueless... (2 Replies)
Discussion started by: bradoyler
2 Replies
3. UNIX for Dummies Questions & Answers
Quick question:
When I load up Terminal or X-Windows on my Mac, and the prompt comes up...what folder am I starting in? (2 Replies)
Discussion started by: liquidcross
2 Replies
4. Windows & DOS: Issues & Discussions
I have been using NetTerm on various Windows flavors for a while and have just run into a problem with printer passthru (transparent printing) that I can analyse but not resolve.
The setup is a Epson TM60 POS Label Printer connected XON/XOFF via COM1 on a Win98SE system. This is controlled... (3 Replies)
Discussion started by: MickZA
3 Replies
5. SCO
I have a file in Unix terminal under $, any command can make this file to be transferred to Windows desktop or C:\, I know that I can use software like FileZilla ftp to transfer file from Unix terminal to desktop. But I am really interested in using command to do this job. anyone knows? (1 Reply)
Discussion started by: wendyz
1 Replies
6. Windows & DOS: Issues & Discussions
Hello all
is there any free tool like linux tabbed terminal but for windows
im used to work with putty and its great but i wander if there something like putty
but with tabs
thanks (12 Replies)
Discussion started by: umen
12 Replies
7. Shell Programming and Scripting
Hi,
How to get unix look and feel in windows environment where i can execute basic commands like date and complex usage like awk, sed etc and not much storage space is needed.
Is there any software that i can install to use the same?
Thanks, (3 Replies)
Discussion started by: i.srini89
3 Replies
8. Linux
Hi All,
Am working in a major IT company, due to security issues, being a fresher am not allowed to install or asking for a specific business reason to install it in my system.
The thing is i want to learn Linux, due to the same security issues we need Admin pass to install certain... (6 Replies)
Discussion started by: mr_ganapathy
6 Replies
9. UNIX for Dummies Questions & Answers
Is there a way to have persistent terminal windows to redhat server across viewer disconnects? I can do that with the help of an extra MS Windows server and rdp, but is there a way of doing that without the Windows server?
Here's the scenario. I have multiple redhat servers (VMs) which have no... (3 Replies)
Discussion started by: ad101
3 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)