General :: Run A Second Command In Same Screen Session?
May 5, 2011
I'm starting the first command in screen like this: screen -d -m -S testen -t lalala watch df -h Now I have a screen session running in background and I can reconnect at a later time. But how can I run a second command (in a new window) in the same screen session?
Is possible (by root of course) to run a command from console, that will be executed on X-session owned by another user on the same linux box/machine ? Example: Can root open xclock for another local user logged into X11 ?
I'm connecting via ssh to an Ubuntu server that has a physical display attached.I'd like the physical display of the server to remain locked while I'm connected remotely.Is this possible? How? Also, is there a way to automatically unlock the screen for the VNC session, which is made from localhost via an ssh tunnel?
I typically have several terminal windows each of which is connected via ssh to a remote server. In each window I work using the gnu screen program, to ensure persistence of the interactive processes in case of a disconnection.
Currently, whenever the ssh connection drops (such as when I put my client computer to sleep overnight) I have to manually and tediously restart the ssh session inside each window, and then in each window tediously resume the specific screen session (e.g. "screen -r 3453" in one window, "screen -r 3462" in the other etc.)
Is there an elegant way to automate this? Specifically:
reconnect the ssh session if it drops, as soon as an Internet connection is detected run the specific screen instance for the terminal window as soon as ssh reconnects
I'm using wmctrl on an Ubuntu machine to manage windows from a script, that I run inside a (gnu) screen.
If I start the screen session from the local machine, wmctrl works fine, including if I completely close the terminal window and issue the wmctrl commands when connecting to the screen remotely via ssh. Conversely, if I connect remotely with ssh and start a screen, wmctrl doesn't work (returns "Cannot open display") even if I attach that screen session locally from the Ubuntu Terminal.
I guess there is some hidden screen parameter that doesn't get set in a way that allows accessing the display when it's launched remotely -- any ideas what it is and how to modify it from within a remote ssh-screen session so that that the script can access the windows?
I have centos 5.3 i got the login screen but after logging shows error as-- your session only last less than 10 seconds . if you have not logged out yourself tyhis could mean that there is some installation problem or that you may out of disk space .try logging with one of fail session.
I am using screen to start a LONG running script on my server over an ssh connection. This works fine. I can see that the script is continuing to run after I disconnect from the screen session using Ctrl-A d. When the script is complete I can reconnect to the screen session and manually terminate it.
I would like to be able to terminate the screen session at the end of the script. I tried issuing an exit command at the end of the script. That did NOT work. Any ideas?
I have debian squeeze server at work, acting as gateway, and home computer with debian sid (amd64). OpenVPN is working on server ecure connections from internet. So my home computer is connected to work server via openvpn almost 24/7. Some days ago i faced strange problem - when i make ssh session from home to work, via openvpn connection, i can login to work server, but after any command on remote console i have blank screen and nothing happening on it. Only exit is pressing Enter ~ . In server's auth log are messages about session opening and closing only.When i ssh to server from local network at workplace - via putty or native ssh - it works without any problems. I can do anything.But from home I can only login.
I recently borked my video driver with a series of upgrades and found my system booting to the TTY with no access to the desktop, graphical login, or even X. I spent some days troubleshooting the problem and experimenting with possible fixes. I found myself wishing for some way to copy and paste from the TTY, or at least log all input and output to a file.
I have installed ubuntu Server 9.10 [ubuntu-9.10-server-i386]in ma machine. After giving the command startx i couldnt goto gui . It saying x session : warning: x rdb command not found resource not merged.
I had chosen automatic logon. Then updated to 10.04. During logout to change Desktop Environment/Session, I noticed that GDM login screen had an option for KDE session although I had not installed KDE. I got curious. So I tried it. System hangs. Restart does not help because somehow gdm proceeds to the KDE session although I did not choose it to be default session. So I had only CLI left.
I got over it by stopping gdm (/etc/init.d/gdm stop) and removing gdm and installing xdm. Anyway, what is the proper way? How to order desktop environment from CLI and/or where is the default desktop environment option written in a file?
Ubuntu have two logout dialogs. One is well known LogOut dialog with Switch User option and second is standalone LogOut dialog from Indicator Applet Session.Did somebody know the command for Indicator Applet Session LogOut dialog?
Is there a command i can enter into the terminal or over an SSH session to make an Ubuntu system reboot a few hours later? Sometimes I want to reboot my server and it should take place in the middle of the night when I'm asleep.
I need a way to have screen (or dbus, whatever) to spit out a list of windows (title and number) that are active in a screen session.I'm writing a wrapper for common work tasks. Part of the functionality will check if a certain window exists, and if so let me know. The idea here is to prevent accessing the same machine twice. (although, and override option would probably be needed, just in case, but I digress...) I've searched through the screen man page and don't see anything that'll work. I'm not beyond forking screen and ending up with a custom version. However, I'd like to avoid that if I can.
Edit: I'd like to see something like "screen -S screen_name -window-list" or similar.
I usually have several xterms open, with each one running a different gnu screen session. It would be useful if--at a glance--I could see the session name in the xterm title bar. That way I would be able to quickly tell which screen sessions are running in which xterms. This would be very useful when alt-tabbing.
I know that there are termcap, terminfo, and termcapinfo commands available, but I don't know how to use these. I also know that there's an $STY environment variable that stores the session name. Also, I do not want to lose my current "hardstatus alwayslastline" bar. It seems like this should be independent from the xterm title, anyways.
This is regarding the 'screen' utility. I use an utility called 'HummingBird Exceed' to get the XSession of a linux client on my windows desktop (basically it uses XDMCP). But the pain is that at the end of the day, when I close Exceed, the session gets destroyed. I did lot of searching on the web to know how the save and restore session in Exceed, but failed. However, I found that 'screen' is the utility which keeps the session intact even when you logout. So, I did the following:
a. Logged into the machine using Putty (terminal emulator).
b. Started 'screen'.
c. Issued the command: /usr/bin/gnome-session
I got the XSession on the Exceed and started working. I opened three or four gnome-terminals. But when I logout of exceed(and detach from the screen), the screen displayed a message saying that 'Connection to XServer was lost". Hence I could not restore to this session when I reattached to the screen. how do I use 'screen' so that when I attach to the screen on which I had started gnome-session, it attempts to connect to the Xserver and open the session as it was before detaching?
I have several screen sessions running, one of them named 'test'. I want to send a simple command to there without attaching the screen, so I do:
screen -S test -X ls
But when I attach the screen to see if it has done something, nothing is different... How can I send commands then? Of course the 'ls' command is not what I want to do, but it's just an example in how this is not working.
I have 2 servers, I set the first one up so that I can remote to it and connect with VNC over ssh by following:[URL]ServerThe 2nd server I did the same, but I cannot connect! When I do, vncviewer prompts for a password and then opens a window of the correct size, but it is all white and then my ssh session is locked! I can't enter any more commands, I have to kill the session.
After running a command that spits out a lot of output in screen. I drop to Copy mode and try to find where the command start. This becomes very very challenging when there are lots of lots of similar text to sift through. Is there a way for me to quickly scroll to where my command starts?
I'd like to use screen to execute a file with a certain session name instead of just numbers... or at least have a more permanent name, I'd like to be able to use it all in one command though. So I can put it into a script.Also: is there a way I can remove or change what comes up at the debian login screen so instead of debain 5.0 I can make it say something else? Also when I login the message that comes up is a little annoying, is there a way I could remove or change that too?
I like very much the Guest Session feature of Karmic, it comes very handy when someone needs to use your computer. However, it's only available if I'm already logged in, it won't show this option at login screen. Is there any way to make this possible? Also, I once tried the guest session and configured its appearance to my taste. The next time I entered, though, the default desktop reappeared. I know this happens because no setting is permanently stored for this session, so the only solution I can think of is to change the default configuration it is loaded from.
Installed Unity from the ppa, restarted the session and got a blank screen.Now I can't figure out how to get back to GDM and reselect Gnome as my default session.
I'm having a really odd problem since I upgraded to 10.04 on my IBM T40 laptop. Every now and then, especially if I'm using Firefox (so it seems), I will be in the middle of something and suddenly I get a black terminal screen that flashes a few lines ending in "checking battery state" and I get bounced back to the login screen. I log back in and all my work is gone (Firefox and whatever else was open has closed). I was on the web for a while tonight and in a few hours it did it three times. I never had this happen before in 9.10.
Any idea what's going on? If it matters I'm on AC power when this is happening. I haven't used it long enough on battery to know if it does it then or not.
I learned how to do this on the 'net somewhere. This HowTo will help you create an account on the login screen that will log in the same guest-session seen in the user menu. The advantage of this is that it will be an easily accessible guest account, while not preserving any files or changes on logout, and a higher security model for the account. Confirmed to work on 10.04 - 10.10, but the directions are for 10.10
1. Under an existing administrator account, go to the menu entry System --> administration --> Users and Groups.
2. Click Add. you may need to provide a password at this point. Name your new user anything you would like, except guest. The account cannot be called guest, but visitor does nicely. encryption of the account is not needed. This account will be a "booster" account to guest-session.
3. On the next screen, enter a password, and make sure that you click the check box "Don't ask for password on login", Click OK to finish.
4. As an extra precaution, click Advanced settings, when back on the Users and Groups screen, and on the User Privileges tab, uncheck Monitor System Logs.
5. Exit the Users and groups menu, and then log out and into your new account.
6. Once there, make a folder called GuestManager, and in that folder, make a plain text file called Guestmanager.sh, with this code in it :
Code: #!/bin/bash # Launches the guest session /usr/share/gdm/guest-session/guest-session-launch # Logs the user when done /usr/bin/gnome-session-save --logout
7. Save that and then right click on it, go to properties, and then go to the permissions tab. On this tab, click "allow executing file as program", and then close that window.
8. Open the menu entry System --> Preferences --> Startup Applications, and once there, turn off all the startup applications, and then click add. Fill in the name and comment as GustManager, and for the command, enter /home/visitor/GuestManager/GuestManager.sh, where visitor would be the name you picked for the account in step 2. click add, then close
9. Delete all applets and extra toolbars (might want to leave the main gnome menu), and set the background to black or something else bland, and log out. Since this account is just a "booster" none of these toolbars and such will be needed, so removing them saves memory and load time.