Tag Info

New answers tagged

2

From man screen: password [crypted_pw] Present a crypted password in your ".screenrc" file and screen will ask for it, whenever someone attempts to resume a detached. This is useful if you have privileged programs running under screen and you want to protect your session from reattach attempts by another user masquerading as your uid ...


0

Some times the multiple screens are running in the background. They can be resumed by: screen -r [pid] To get the screen, first run screen -R, then you will see all the running PIDs of screen, after that resume by screen -r [pid].


1

I have a python script that keeps track of numerous detached screen sessions and captures output from each (when utilization commands like free, top -bn2, iostat are periodically sent via 'stuff'). Instead of redirecting to a file and, thus, managing at least one file per detached screen session... I simply redirect to whatever tty/pts my parent session is ...


0

mhahn said there was a bug in Yocto sshd killing all current cgroup processes when leaving ssh which has an easy fix (just didn't make it to the Edison build yet): poky - Poky Build Tool and Metadata i.e. in short: echo "KillMode=process" >> /lib/systemd/system/sshd@.service https://communities.intel.com/thread/57402?start=15&tstart=0


3

You can check this or better you can check man page for screen which is a good reference and says: backtick id lifespan autorefresh cmd args... backtick id Program the backtick command with the numerical id id. The output of such a command is used for substitution of the "%`" string escape. The specified lifespan is the number of seconds the ...


1

screen sessions are not killed/terminated when the attaching terminal goes away. They are detached just as if you had detached manually (using Ctrl-a d, probably). That's part of the point of screen. The disappearance of your screen session is due to some other reason. Perhaps the shell running inside the screen exited on its own or the server got rebooted ...


0

I've had success getting basic paging by piping content to more, for example: ls -l | more Or, if you want color output for use cases like syntax highlighting, you can use ls -l --color=always | more This results in output that I can easily page through one screen at a time. I haven't tried @uther's modification to ~/.screenrc but that does seem ...


4

The parent process id (ppid) of a process cannot be changed outside of the kernel; there is no setppid system call. The kernel will only change the ppid to (pid) 1 after the processes parent has terminated - if the process did not respond to a signal that the parent was terminated. For this to happen, the process needs to have ignored various signals ...


0

No, starting a screen session after a process is started will not help. What you can try is just putting the process in the background. On my Linux (Mint 17) I tried it with another shell and put 'sleep 100000` in the background. Then I logged off the session and started a new one. The sleep 100000 process was still running and the parent became process 1 ...


0

No. Your Matlab output will not magically appear in the screen session for that you need to first start screen then start the matlab session within it. The same holds true for tmux. If you want to reconnect the stdin/out of this running process to another you can try reptyr


0

I find that while screen doesn't interpret named characters such as \n, it does take care of octal escapes. So instead of stuff 'echo "The array has of elements."\n', you could use: stuff 'echo "The array has of elements."'\012


0

You don't mention using a null modem with your serial cable, perhaps that is why you never see anything in the terminal. Since the device is booting, then U-boot is working properly. Your serial settings are correct as defined in to the release notes and the serial console instructions provided on the Toradex developer website. Ensure that you use a null ...


2

Following a comment suggested in the post I used: screen -x <session id> From the man page: screen -x -x Attach to a not detached screen session. (Multi display mode). Screen refuses to attach from within itself. But when cascading multiple screens, loops are not detected; take care. Also researching a bit I discovered other uses for ...


7

You should be creating screens with names. $ screen -S foo $ screen -list There are screens on: 16994.foo (03/30/15 14:05:13) (Detached) 20082.q (12/17/14 18:06:44) (Detached) 11008.w (11/12/14 10:52:43) (Detached) 1199.irc (11/12/14 01:34:40) (Detached) Then you can reattach screens with $ ...


9

Sure, with screen -d -r You can choose which screen to detach and reattach as usual by finding the pid (or complete name) with screen -list. screen -d -r 12345



Top 50 recent answers are included