default session in screen command Post: 302303081

9 More Discussions You Might Find Interesting

1. 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. ...

2. Programming

how to clear screen in GDB session

hi , Could any one tell me the command for clearing the screen in GDB session

3. UNIX for Dummies Questions & Answers

the command to save session

I remember there is a command you can type and it records everything you type on after it...anybody can help a bit?

4. 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. 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...

6. Red Hat

command line tool to disable screen lock and/or screen saver

Hi, I have a simple question : how to disable screen lock and/or sreen saver with command line with RHEL5.4 ?

7. 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...

8. HP-UX

Get blank screen when killing a UNIX session on HP-UX

Hi, I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen? Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second...

9. 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...

LEARN ABOUT LINUX

user-session-keyring

USER-SESSION-KEYRING(7) 				     Linux Programmer's Manual					   USER-SESSION-KEYRING(7)

NAME

       user-session-keyring - per-user default session keyring

DESCRIPTION

       The  user  session  keyring  is a keyring used to anchor keys on behalf of a user.  Each UID the kernel deals with has its own user session
       keyring that is shared by all processes with that UID.  The user session keyring has a name (description) of the form _uid_ses.<UID>  where
       <UID> is the user ID of the corresponding user.

       The  user  session  keyring  is	associated  with the record that the kernel maintains for the UID.  It comes into existence upon the first
       attempt to access either the user session keyring, the user-keyring(7), or the session-keyring(7).  The keyring remains pinned in existence
       so  long as there are processes running with that real UID or files opened by those processes remain open.  (The keyring can also be pinned
       indefinitely by linking it into another keyring.)

       The user session keyring is created on demand when a thread requests it or when a thread asks for its session-keyring(7) and  that  keyring
       doesn't	exist.	In the latter case, a user session keyring will be created and, if the session keyring wasn't to be created, the user ses-
       sion keyring will be set as the process's actual session keyring.

       The user session keyring is searched by request_key(2) if the actual session keyring does not exist and is ignored otherwise.

       A special serial number value, KEY_SPEC_USER_SESSION_KEYRING, is defined that can be used in lieu of the actual serial number of the  call-
       ing process's user session keyring.

       From the keyctl(1) utility, '@us' can be used instead of a numeric key ID in much the same way.

       User  session keyrings are independent of clone(2), fork(2), vfork(2), execve(2), and _exit(2) excepting that the keyring is destroyed when
       the UID record is destroyed when the last process pinning it exits.

       If a user session keyring does not exist when it is accessed, it will be created.

       Rather than relying on the user session keyring, it is strongly recommended--especially if the process is running as root--that a  session-
       keyring(7) be set explicitly, for example by pam_keyinit(8).

NOTES

       The user session keyring was added to support situations where a process doesn't have a session keyring, perhaps because it was created via
       a pathway that didn't involve PAM (e.g., perhaps it was a daemon started by inetd(8)).  In such a scenario, the user session  keyring  acts
       as a substitute for the session-keyring(7).

SEE ALSO

       keyctl(1), keyctl(3), keyrings(7), persistent-keyring(7), process-keyring(7), session-keyring(7), thread-keyring(7), user-keyring(7)

Linux								    2017-03-13						   USER-SESSION-KEYRING(7)