Sponsored Content
Operating Systems Linux Fedora default session in screen command Post 302303134 by pludi on Thursday 2nd of April 2009 01:16:07 AM
Old 04-02-2009
That session isn't created by the OS, but by screen itself, and the naming convention used for the socket is <pid of screen>.<tty where invoked>.<hostname>
You can see this information if you enter "screen -ls" after starting a screen session. If there are no sockets, there are no screen sessions you can re-attach to.
 

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. ... (0 Replies)
Discussion started by: Blooper
0 Replies

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

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? (2 Replies)
Discussion started by: fedora
2 Replies

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 Replies)
Discussion started by: akula_1986
5 Replies

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... (1 Reply)
Discussion started by: kylecn
1 Replies

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 ? (1 Reply)
Discussion started by: albator1932
1 Replies

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... (6 Replies)
Discussion started by: dustytina
6 Replies

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... (5 Replies)
Discussion started by: rm-r
5 Replies

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... (7 Replies)
Discussion started by: prvnrk
7 Replies
CEREAL-ADMIN(8) 					      Administration Commands						   CEREAL-ADMIN(8)

NAME
cereal-admin - administer cereal sessions SYNOPSIS
cereal-admin command [args] DESCRIPTION
cereal-admin is a program to administer cereal sessions. A cereal session is a special (restricted) screen(1) session attached to a serial terminal. Each cereal session is owned by a particular user (USER) who is allowed to "attach" to the cereal screen session and interact with the specified serial terminal via screen. Each cereal session is also associated with a particular log group (LOGGROUP) whose members are allowed to "follow" the logs of the session. Cereal was designed to monitor serial lines connected to the serial consoles of remote machines. The cereal system is outlined at: http://cmrg.fifthhorseman.net/wiki/cereal SUBCOMMANDS
cereal-admin takes various subcommands: create SESSION TTY BAUD USER LOGGROUP Create a new session named SESSION on tty TTY, with baud rate BAUD. USER is the user that will own the session, and LOGGROUP is the group that will be able to follow the session non-interactively (ie. read the logs). Once created, the session will be in a "stopped" state. `c' may be used in place of `create'. start [options] SESSION [SESSION]... Start session(s). For each session specified, the session directory is registered in the runsvdir directory. The screen session will be attached to the serial terminal and logging of the terminal will begin. `s' may be used in place of `start'. options: -a (--all) to enable all sessions. restart [options] SESSION [SESSION]... Restart session(s). This sends running sessions a "restart" signal, and starts session that are not running. This can be used when changes have been made to the screenrc, for instance. `r' may be used in place of `restart'. options: -a (--all) to disable all sessions, -r (--running) to restart just the currently running sessions. stop [options] SESSION [SESSION]... Stop session(s). This kills the screen session attached to the serial terminal by sending it an "exit" signal, and then unregister- ing the session directory from the runsvdir directory. `k' may be used in place of `stop'. options: -a (--all) to disable all ses- sions. destroy [options] SESSION [SESSION]... Destroy session(s) entirely. This will destroy the session directory, including all history of the session and the logs. `d' may be used in place of `destroy'. options: -a (--all) to remove all sessions. list [SESSION]... List session(s). With no arguments, will list all sessions. The leading three characters in the list indicate: whether the session is running (+) or not (-) or in some unknown state (?), whether the user can attach to the session (a) or not (-), whether the user can follow the session (f) or not (-). If the session state is unknown (?), it's usually because the user asking for information about the session can't read the session stat file. `l' may be used in place of `list'. help Output a brief usage summary. `h' or `?' may be used in place of `help'. LOGS
Logs are handled by svlogd. For information on how to control session log handling, please see svlogd(8) and/or log-limits.txt from the documentation of this package. FILES
/etc/cereal/screenrc Default cereal screenrc file. /etc/cereal/cereal-admin.conf Configuration file to set parameters for session creation and management. /var/lib/cereal/sessions/$SESSION/screenrc Special screenrc file for session SESSION. The presence of this file overrides the default screenrc file /etc/cereal/screenrc. EXIT STATUS
Exit status is 0 if OK, 1 if minor problems, 2 if serious trouble. AUTHOR
Written by Jameson Rollins and Daniel Kahn Gillmor. BUGS
If the invoking user does not have read and execute access to the cereal session's supervise directory, `cereal-admin list' may not always indicate that session's status accurately. REPORTING BUGS
Report bugs to <cereal@fifthhorseman.net>. COPYRIGHT
Copyright (C) 2007 Jameson Rollins and Daniel Kahn Gillmor This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
cereal(1), screen(1), runsvdir(8), svlogd(8) cereal-admin 0.1 March 2007 CEREAL-ADMIN(8)
All times are GMT -4. The time now is 08:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy