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
LOGINCTL(1)							     loginctl							       LOGINCTL(1)

NAME
loginctl - Control the systemd login manager SYNOPSIS
loginctl [OPTIONS...] {COMMAND} [NAME...] DESCRIPTION
loginctl may be used to introspect and control the state of the systemd(1) login manager systemd-logind.service(8). OPTIONS
The following options are understood: -h, --help Prints a short help text and exits. --version Prints a short version string and exits. -p, --property= When showing session/user/seat properties, limit display to certain properties as specified as argument. If not specified, all set properties are shown. The argument should be a property name, such as "Sessions". If specified more than once, all properties with the specified names are shown. -a, --all When showing session/user/seat properties, show all properties regardless of whether they are set or not. -l, --full Do not ellipsize process tree entries. --no-pager Do not pipe output into a pager. --no-ask-password Do not query the user for authentication for privileged operations. --kill-who= When used with kill-session, choose which processes to kill. Must be one of leader, or all to select whether to kill only the leader process of the session or all processes of the session. If omitted, defaults to all. -s, --signal= When used with kill-session or kill-user, choose which signal to send to selected processes. Must be one of the well known signal specifiers, such as SIGTERM, SIGINT or SIGSTOP. If omitted, defaults to SIGTERM. -H, --host Execute operation remotely. Specify a hostname, or username and hostname separated by "@", to connect to. This will use SSH to talk to the remote login manager instance. -P, --privileged Acquire privileges via PolicyKit before executing the operation. The following commands are understood: list-sessions List current sessions. session-status [ID...] Show terse runtime status information about one or more sessions. This function is intended to generate human-readable output. If you are looking for computer-parsable output, use show-session instead. show-session [ID...] Show properties of one or more sessions or the manager itself. If no argument is specified, properties of the manager will be shown. If a session ID is specified, properties of the session are shown. By default, empty properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=. This command is intended to be used whenever computer-parsable output is required. Use session-status if you are looking for formatted human-readable output. activate [ID...] Activate one or more sessions. This brings one or more sessions into the foreground, if another session is currently in the foreground on the respective seat. lock-session [ID...], unlock-session [ID...] Activates/deactivates the screen lock on one or more sessions, if the session supports it. lock-sessions, unlock-sessions Activates/deactivates the screen lock on all current sessions supporting it. terminate-session [ID...] Terminates a session. This kills all processes of the session and deallocates all resources attached to the session. kill-session [ID...] Send a signal to one or more processes of the session. Use --kill-who= to select which process to kill. Use --signal= to select the signal to send. list-users List currently logged in users. user-status [USER...] Show terse runtime status information about one or more logged in users. This function is intended to generate human-readable output. If you are looking for computer-parsable output, use show-user instead. Users may be specified by their usernames or numeric user IDs. show-user [USER...] Show properties of one or more users or the manager itself. If no argument is specified, properties of the manager will be shown. If a user is specified, properties of the user are shown. By default, empty properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=. This command is intended to be used whenever computer-parsable output is required. Use user-status if you are looking for formatted human-readable output. enable-linger [USER...], disable-linger [USER...] Enable/disable user lingering for one or more users. If enabled for a specific user, a user manager is spawned for him/her at boot and kept around after logouts. This allows users who are not logged in to run long-running services. terminate-user [USER...] Terminates all sessions of a user. This kills all processes of all sessions of the user and deallocates all runtime resources attached to the user. kill-user [USER...] Send a signal to all processes of a user. Use --signal= to select the signal to send. list-seats List currently available seats on the local system. seat-status [NAME...] Show terse runtime status information about one or more seats. This function is intended to generate human-readable output. If you are looking for computer-parsable output, use show-seat instead. show-seat [NAME...] Show properties of one or more seats or the manager itself. If no argument is specified, properties of the manager will be shown. If a seat is specified, properties of the seat are shown. By default, empty properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=. This command is intended to be used whenever computer-parsable output is required. Use seat-status if you are looking for formatted human-readable output. attach [NAME] [DEVICE...] Persistently attach one or more devices to a seat. The devices should be specified via device paths in the /sys file system. To create a new seat, attach at least one graphics card to a previously unused seat name. Seat names may consist only of a-z, A-Z, 0-9, "-" and "_" and must be prefixed with "seat". To drop assignment of a device to a specific seat, just reassign it to a different seat, or use flush-devices. flush-devices Removes all device assignments previously created with attach. After this call, only automatically generated seats will remain, and all seat hardware is assigned to them. terminate-seat [NAME...] Terminates all sessions on a seat. This kills all processes of all sessions on a seat and deallocates all runtime resources attached to them. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. ENVIRONMENT
$SYSTEMD_PAGER Pager to use when --no-pager is not given; overrides $PAGER. Setting this to an empty string or the value "cat" is equivalent to passing --no-pager. SEE ALSO
systemd(1), systemctl(1), systemd-logind.service(8), logind.conf(5) systemd 208 LOGINCTL(1)
All times are GMT -4. The time now is 11:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy