Sponsored Content
Operating Systems HP-UX Get blank screen when killing a UNIX session on HP-UX Post 302919191 by rm-r on Monday 29th of September 2014 12:02:07 PM
Old 09-29-2014
Could someone running HP-UX please run my test above and let me know if you also get the blank screen.

I am starting to wonder if my terminal emulator is not the culprit here.

Thanks.
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Killing Idle session

does any one know how to kill an idle session? I want to kill any idle sessions after 30 min... Local or remote.... i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure..... ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies

2. Shell Programming and Scripting

My screen saver for a plain session

Good day. :) I don't know exactly where or how to post this kind of stuff, but I though I'd like to have a look at my "Screen Saver" in progress. Comments welcome. This uses bash. Just copy and pase into any file. Make o+x and run. Feel free to edit and change all u like. Thanks. ... (0 Replies)
Discussion started by: Blooper
0 Replies

3. Programming

how to clear screen in GDB session

hi , Could any one tell me the command for clearing the screen in GDB session (1 Reply)
Discussion started by: useless79
1 Replies

4. Shell Programming and Scripting

Help in killing the session !

Hello, I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem. my script is, --- while true do ./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt echo "Restarting `date`" done --- As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies

5. Fedora

default session in screen command

Hello sir, Im in a Fedora 9 system. Im using screen to invoke the session that is created by me. Whenever we open the terminal then a session is created by the operating system. I want to know what is the name of default session in screen command. I could not get it using "screen -ls". Can you... (3 Replies)
Discussion started by: nsharath
3 Replies

6. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

7. Shell Programming and Scripting

Print from screen session

Hello everyone, Following command sends word 'test' followed by an enter into a screen session (in our case screen_1). How do I print the result, if that would result ? How do I print the result, even if the program running in the session is locked ? Thank you :) screen -S screen_1 -X... (5 Replies)
Discussion started by: akula_1986
5 Replies

8. Shell Programming and Scripting

Script that prints 2 messages to a screen session

Im trying to make a script that prints 2 messages to a screen session, one after the other. screen -x session44 -X stuff "`printf "Test 1\r"`" This works fine, but adding a second lien with a different message yields no results. Changed Subject: Please Follow Forum Rules Regarding... (1 Reply)
Discussion started by: kylecn
1 Replies

9. Shell Programming and Scripting

Unix scripting and screen session

hi, i am on AIX 5.3. I would like to write scripts that initiate or reattach to a screen session to run some commands either from unix or Universe. Can anyone assist me with a with a wuick primer on this. I can attach or initiate a screen manually and then run the commands but I would like to... (6 Replies)
Discussion started by: dustytina
6 Replies

10. Linux

Is it possible to set timeout on Linux screen session

Hello friends, I work on Linux servers via SSH (putty) and run "screen" to preserve my sessions so I can attach/detach them at anytime I wish without losing the connectivity/process disruption which is working perfectly fine. As my team members also have root access to those servers, it is... (7 Replies)
Discussion started by: prvnrk
7 Replies
WMANAGER-LOOP(1)					    BSD General Commands Manual 					  WMANAGER-LOOP(1)

NAME
wmanager-loop -- loop running window managers chosen with wmanager SYNOPSIS
wmanager-loop [OPTIONS ...] DESCRIPTION
The wmanager-loop program starts either the window manager specified by the WM variable or the first window manager listed in ~/.wmanagerrc (or an X terminal emulator if none), and when it exits, runs wmanager(1) to prompt the user for the next window manager. It loops doing this until the user chooses ``Exit this session'' in wmanager(1). Any options given to wmanager-loop will be passed on to wmanager(1). If the WM environment variable is set, the wmanager-loop program tries to interpret it as a window manager specification in the following ways in the specified order: o a full path to an executable file to run as the window manager; o the name of a window manager listed in the /.wmanagerrc file; e.g. ``fluxbox'' would match the following line: fluxbox=/usr/bin/startfluxbox o the program name of a window manager listed in the /.wmanagerrc file; e.g. ``startfluxbox'' would match the above example. o the start of such a program name; e.g. ``start'' would match the above example. o the end of such a program name; e.g. ``box'' would match the above example. If the WM variable is set and there is more than one line in ~/.wmanagerrc that matches the specification, wmanager-loop will exit with an error message. As mentioned above, if no window manager is specified in the WM environment variable or found in the ~/.wmanagerrc file, the wmanager-loop program attempts to start an X terminal emulator. If the WMTERM environment variable is set, the wmanager-loop program uses it as the path to the emulator. Otherwise it searches the user's path for a program named ``x-terminal-emulator'', ``urxvt'', ``rxvt'', or ``xterm'' in this order, and starts the first one found using its full path. If none of the common terminal emulators on the above list is found, the wmanager-loop program just runs ``xterm'' in the hope that something will come up on the user's display. ENVIRONMENT
The wmanager-loop program uses the following environment variables: WM The name, path, or partial path to the first window manager to execute. WMTERM The name of the X terminal emulator to execute if no window manager could be found in the ~/.wmanagerrc file. If not specified, the wmanager-loop program searches the user's path as described above. EXAMPLE
To start using wmanager-loop, create a ~/.wmanagerrc file - generally with wmanagerrc-update(1) - and add something like the following at the end of your ~/.xsession file: exec wmanager-loop -geometry +570+585 SEE ALSO
wmanager(1), wmanagerrc-update(1) HISTORY
The wmanager-loop program was written by Tommi Virtanen in 2000 and later modified by Peter Pentchev. This manual page was originally writ- ten in perldoc format by Tommi Virtanen in 2000, and converted to mdoc format and updated by Peter Pentchev in 2008. AUTHORS
Tommi Virtanen <tv@debian.org> Peter Pentchev <roam@ringlet.net> BSD
September 8, 2009 BSD
All times are GMT -4. The time now is 05:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy