Persistent Terminals For a Dedicated Computing Box? 288
Theovon writes "I just built a high-end quad-core Linux PC dedicated to number-crunching. Its job is to sit in the corner with no keyboard, mouse, or monitor and do nothing but compute (genetic algorithms, neural nets, and other research). My issue is that I would like to have something like persistent terminal sessions. I've considered using Xvnc in a completely headless configuration (some useful documentation here, here, here, and here). However, for most of my uses, this is overkill. Total waste of memory and compute time. However, if I decided to run FPGA synthesis software under WINE, this will become necessary. Unfortunately, I can't quite figure out how to get persistent X11 session where I'm automatically logged in (or can stay logged in), while maintaining enough security that I don't mind opening the VNC port on my firewall (with a changed port number, of course). I'm also going to check out Xpra, but I've only just heard about it and have no idea how to use it. For the short term, the main need is just terminals. I'd like to be able to connect and see how something is going. One option is to just run things with nohup and then login and 'tail -f' to watch the log file. I've also heard of screen, but I'm unfamiliar with it. Have other Slashdot users encountered this situation? What did you use? What's hard, what's easy, and what works well?"
Screen works welll (Score:5, Informative)
Re: (Score:2)
Screen works for text. Does it allow persistent and secure connections for types of programs mentioned in the article?
Re:Screen works welll (Score:4, Informative)
Screen is a most excellent utility for persistent terminals, but (as far as I know) it will not let you keep persistent X11 information.
Re:Screen works welll (Score:4, Informative)
If for whatever reason I lose the connection, I can start ssvnc again and get the desktop back.
Re:Screen works welll (Score:5, Informative)
Re:Screen works welll (Score:5, Informative)
The article seemed to mention 2 stages, first needing persistant terminals, which screen is PERFECT for... The second stage will require wine, which means X, which means VNC...
The guy has answered his own questions.
Re:Screen works welll (Score:5, Informative)
My understanding, which might be wrong, is that you can't do this with just screen and an ssh-forwarded X server.
In X, for those that don't know, applications are clients and the display is the server. So when you run apps from your server box and display them on your laptop, the app on the server box is the client and your laptop display is the server.
An X client needs to be connected to an X server. I think it would be possible to write ones that could handle dropping and resuming their server connections, but I don't think any programs actually act this way in practice. So to have clients running persistently while you're not connected you need a locally-running X server that those clients remain connected to. The traditional thing to do, then, is to use VNC to let other computers access that local X session. Compared to what you were doing, forwarding the actual X connection over SSH, this has the advantage that a smart VNC client/server can adjust for slow network connections by combining messages to be sent, remembering the display state on the client side so window redraws (as a result of overlapping windows) don't require any network activity, and image compression (for some kinds of windows sending an X11 command stream is more efficient than sending compressed image data, but for others it's the other way).
The VNC protocol, however, doesn't have many security features built in, and there are lots of different client-server combinations that use non-standard or semi-standard compression techniques. The standard answer to VNC's lack of built-in security features is to forward VNC connections through SSH. That, plus any modern VNC client-server combo, generally gets the job done. But there's a relatively new program that essentially is a better VNC. It's called NoMachine. Google it. For some uses it's free-as-in-beer, and I think they release some source code, but they are a for-profit company and generally use a proprietary model IIRC. If that doesn't bother you, their product is good as far as I've seen. If you want to stay with Free Software, you'll probably want VNC+SSH.
Re:Screen works welll (Score:5, Interesting)
Why not just run it on the console, and connect a KVM with network access to that sucker?
Long term != poor comprehension (Score:3, Informative)
From the article: For the short term, the main need is just terminals.
(my strong emphasis)
I would guess mrmeval was looking at "However, if I decided to run FPGA synthesis software under WINE, [some system that supports graphics] will become necessary." in the article. I don't think this FPGA synthesis software can be operated completely from the command prompt.
Re: (Score:2)
Re: (Score:2)
Altera's can too (we used to use it from a Makefile at a previous company I worked for.) Unfortunately, they charge money for their Linux-native version, which is a bummer since it's quite a bit faster than the Windows version, or at least was at that time.
Re:Screen works welll (Score:5, Informative)
Agreed. I built something like that a few years ago. It had a vt100 sitting on top of it and I used screen to keep up with the data. Screen is easy to use. The only real command that you will need is screen -R. The -R will tell it to resume the screen session in the background and if there isn't one to create it.
Re:Screen works welll (Score:5, Informative)
Re: (Score:2, Informative)
Re: (Score:2)
Yes, -x is one of it's more useful features. I use it to check the output on the console in the system room from my office.
Re:Screen works welll (Score:5, Informative)
Re:Screen works welll (Score:5, Informative)
The quick primer:
First time:
ssh mymachine
screen
<do some work>
CTRL-a-c <create another login session>
<do some more work in diff dir>
CTRL-a-1 <back to first login session>
CRTL-a-d <disconnect>
exit
Future times:
ssh mymachine
screen -r <resume screen>
CTRL-a-2 <back to second login session>
<do some work>
CTRL-a-d <disconnect>
exit
You can create many login sessions inside one screen instance or launch multiple instances of screen on the same box by giving them a name. See the man page for all the goodness.
Re: (Score:3, Interesting)
If all you are doing is establishing a persistent ssh connection, you may want to think about using dtach [sourceforge.net]. It's the equivalent of vi to emacs. Why use an operating system when all you need is a text editor?
Re: (Score:2)
Re: (Score:3, Interesting)
Of course you can, and its one of the more useful features of screen.
MultiUser sessions [ualberta.ca]
You configure ACL's per user, allowing you to give someone read access to your screen but not actually giving them control. This works really well for demonstrations.
It's also a very convenient way to demonstrate to another user on the system some sort of odd behavior you're experiencing, or get feedback on something.
As for the security of it, if security was a serious concern you shouldn't run things in a multiuser syste
Re: (Score:2, Funny)
Re:Screen works welll...read this link SUBBY (Score:3, Informative)
so is google. im not against people looking for help, but i would think ask slashdot could limit itself to unusual problems. ssh/x forwarding/screen is pretty elementary stuff.
what a ridiculous thing to put on the front page. any number of forums or HOWTOs probably provide all the information the submitter is looking for, so id like him to read this.it looks long, but its a quick read.
How to ask questions the smart way [linuxmafia.com]
Re:Screen works welll...read this link SUBBY (Score:4, Informative)
Easy; plug in the Ethernet, boot a Gentoo LiveCD, and a minute after the disc access has stopped, type the following (carefully) at the assumed # prompt:
# ifconfig eth0 [a known IP] /etc/init.d/ssh start
#
# passwd
[enter a password for root, twice]
SSH in from another box, and you're done! Worked fine for me, installing Gentoo on a Kanga with a broken screen from three timezones away.
Of course, it assumes that the Ethernet card is working, and that the kernel picks it up as eth0. If the network lights up but you get no joy, try a LAN-wide ping sweep; I've had to do that a coupla times when this kinda thing's cropped up.
How about NX/nomachine.com? (Score:5, Informative)
Captain Obviousman.
Re:How about NX/nomachine.com? (Score:5, Informative)
Yeah, it's not free as in speech, but otherwise beats the crap out of vnc.
Captain Obviousman.
FreeNX is free and works to what he wants as well.
Re: (Score:3, Informative)
From my experience, everything keeps running. All the "suspend" does is leave your X-session open, so you can reconnect to it later.
"Terminate" kills any open apps and logs out of that X-session.
Re: (Score:2)
I've got it running on my personal machines which are sitting in a colo. It runs over SSH which is great and I locked down SSH to only allow "trusted" users and everything works great! I haven't played with it's Samba integration but it's supposed to allow you to share files from your windows Client with your NX session. Also NX will apparently pipe audio across the link but I haven't played with this yet. For my needs it's been perfect.
Oh ya... the server (Linux) and client (Windows/Linux) are both fre
ssh + vnc (Score:5, Informative)
You could use VNC, but set it up so the vnc server is only accessible via localhost, and then use ssh to create a secure tunnel back to your client. Alternatively I sometimes use vnc and ssh with X11 forwarding, i.e. the actual graphical data being sent over the network is over X11 as opposed to VNC's protocol.
screen is cool and pretty easy to use, RTFM. But its command-line only, so not applicable if you need GUI as well.
Re: (Score:3, Informative)
Re: (Score:3, Informative)
If you use xtightvncviewer, it has the "-via" option which sets up a tunnel (ssh is the default) for the connection. Only ssh needs to be exposed through the firewall that way.
Alternatively, set up OpenVPN (either through a dedicated firewall or on your linux box) or other VPN so you can access the VNC server as if you were local to your network.
Re: (Score:2)
I wouldn't personally log into an account via a public terminal, unless I was using a one time password set up or it was a junk account.
Considering the person asking the question has control of his own box, that's definitely doable without too much trouble. The only other bit is having the calculator or printed card.
screen (Score:2, Informative)
Yum distro:
yum install screen
man screen
Apt distro:
apt-get install screen
man screen
Re: (Score:3, Informative)
emerge -av screen
Mac OS X:
fink install screen
Re: (Score:2)
That or:
sudo port -v install screen
Re: (Score:2)
Actually, for Mac OS X it's even simpler, as screen comes with the base OS:
mymac:~ username$ which screen
/usr/bin/screen
Re:screen (Score:5, Funny)
Slackware distro: /usr/src/tar .. /tmp/screen_install /tmp/screen_install /usr/src/packages ..
cd
wget ftp://ftp.gnu.org/gnu/screen/screen-4.0.2.tar.gz [gnu.org]
cd
tar -xzf tar/screen-4.0.2.tar.gz
cd screen-4.0.2
CFLAGS=" -O2 -march=pentium-m -pipe -fomit-frame-pointer"./configure --prefix=/usr
make
mkdir
make DESTDIR=/tmp/screen_install install
cd
mkdir install
vim install/slack-desc
makepkg screen-4.0.2-i686-1.tgz
installpkg screen-4.0.2-i686-1.tgz
cp screen-4.0.2-i686-1.tgz
cd
rm -r screen_install
What? Difficult? What are you talking about, that's the only good way.
Re: (Score:2)
Stop frightening the non-slackers, screen is in the disto slashdoters.
1.Insert dvd or download slackpack from ftp.slackware.com (Hey you could even use your browser!) /{directory containing package}
2.cd
3.installpkg screen-X.X.X-i386-1.tgz (replace X as required: hint match the file name.)
A bit easier then the above I think, and no you won't get any uber-leet-performance by doing your own build.
Use screen (Score:2, Informative)
Nothing beats screen for terminals.
I use irssi + screen so I can be in some of my irc channels all the time, and connect to it from wherever I can run an ssh client.
Go with screen (Score:2, Informative)
Given that it's made specifically for persistent terminals across login sessions, Screen is definitely worth learning. If your needs are text-based, it's the best way to go.
It sounds like your GUI needs are rare. In those occasions you could probably fire up a VNC or other session when you need it (from the remote screen session) and shut it down again when you're done.
screen (Score:5, Insightful)
Re:screen (Score:5, Insightful)
Screen is one of the greatest and useful commands ever envisioned.
Re:screen (Score:4, Informative)
And of course my favorite thing in my .screenrc:
# turn sending of screen messages to hardstatus off
hardstatus on
# Set the hardstatus prop on gui terms to set the titlebar/icon title
termcapinfo xterm*|rxvt*|kterm*|Eterm* hs:ts=\E]0;:fs=\007:ds=\E]0;\007
# use this for the hard status string
hardstatus alwayslastline
#hardstatus string "%h%? users: %u%?"
hardstatus string "%{.bW}%-w%{.rW}%n %t%{-}%+w %=%{..G} %H %{..Y} %m/%d %C%a "
Re: (Score:3, Informative)
Re: (Score:2)
Re: (Score:2)
Yes, that is true. It one of the most useful applications then.
Simple answers. (Score:5, Informative)
stupid question (Score:2)
Yeah it makes sense (Score:3, Informative)
All code except system calls runs natively, and therefore just as fast as native code.
Re: (Score:2)
Re: (Score:3, Interesting)
That's true, but if he's talking about graphics things, there is a LOT that is emulated. Google "DIB engine wine" for a look.
Basically, unless you're using DirectX/OpenGL, windows makes assumptions about the graphics layer that can't be directly done in X. AFAIK (it's hard to understand), many of the earlier windows libraries give the program direct shared access to where they are rendering, but X11 has the program and the actualy framebuffer divided by the X11 layer. Emulating that blows in terms of perfor
freenx / nxserver (Score:5, Informative)
For persistent GUI sessions, I generally use nx/nxserver/freenx:
http://freenx.berlios.de/ [berlios.de]
For console sessions, nothing beats "screen". I use the command "screen -m -R" to create and/or reconnect to an existing session.
I used to like VNC, but I got tired of how difficult it was to set up. On Windows boxes, I stick to Remote Desktop Connection.
nx* = PITA (Score:4, Interesting)
You think VNC is difficult to set up? Well NX is just absurdly complicated. That one time I managed to get it working, it was indeed vastly superior to VNC, but I just can't fucking understand why they have to install their own damn SSH server and keys. Why? WHY???
How come it's not been picked up by any major distribution? Probably because installing it by following the megabyte-long HOWTOs feels like an exercise in computer masochism.
Re:nx* = PITA (Score:4, Informative)
Not seperate ssh server... unless you're on Windows?
Separate key is needed because nx must do session/login management from root. Simple as that. Once I grasped that, the rest came easy (I will admit to being familiar with ssh configuration though).
Re: (Score:2)
How come it's not been picked up by any major distribution?
SuSE has had it for a while now. My recollection of seeing it in YAST goes back at least a year. It's a *SNAP* to setup under SuSE. Select the package, then go to the docs directory and read the SuSE readme, run the setup program. Done, less than 10 minutes start to finish. If anything the windows client is more confusing than the Linux server under SuSE. :-)
FWIW, nxserver works great (Score:3, Informative)
...I've always had more luck getting it to work right than with freenx. But the latter has a KDE session integration now so the auther may want to look into that.
The session handling and preservation of nxserver is very good.
Re: (Score:2)
I've always found VNC dead-simple to install/configure/run, except on the cruftiest of old unix systems where the environment setup was busted.
Typically it's one-liner native package install, run 'vncserver', and change your window manager if you're picky.
Screen. (Score:2)
Keep it simple - this is what screen was meant for. Install it and read the man page, it's really easy to use.
Persistent X and others (Score:5, Informative)
http://www.icsi.berkeley.edu/~wooters/persistentX.html [berkeley.edu]
I've not tried this but it looks good.
Some for vnc
http://www.novell.com/coolsolutions/feature/16011.html [novell.com]
With xinetd?
http://newsgroups.derkeiler.com/Archive/Uk/uk.comp.os.linux/2006-02/msg00109.html [derkeiler.com]
SSH Tunnel to protect VNC (Score:5, Informative)
This is what I do every morning to get into work.
Start up a VNC server on the remote box and leave it running. No need to open holes in your firewall except for SSH, which is pretty safe to do.
To tunnel through the firewall and log in, type these commands on your local machine:
Voila: VNC connection, secured by SSH. When you are done just
. :1 VNC session, 5902 means :2, etc.
Note that 5901 means the
Re:SSH Tunnel to protect VNC (Score:5, Informative)
Re: (Score:2)
and if you use pageant, password is a one-time affair. However, if he's using a closed-lan system, then he could use a passwordless key so he can SSH on just by clicking a link.
Re:SSH Tunnel to protect VNC (Score:5, Interesting)
No need to open holes in your firewall except for SSH, which is pretty safe to do.
I would strongly disagree with this statement. Because ssh has the ability to do so much, it deserves special attention to security. The default implementation should be tweaked more than a little bit, including disabling password login, changing the port and, please don't forget, disabling ssh1. There are other, more subtle, cryptographic attacks, but even those few changes should make it more secure.
Re: (Score:2)
The default implementation should be tweaked more than a little bit, including disabling password login, changing the port and, please don't forget, disabling ssh1.
Disabling passwords is a double-edged sword. On the one hand, it's more difficult to forge credentials, but on the other hand, a stolen, carelessly-maintained laptop grants full access. Either way, you trust the end-user to secure her system -- it's just that with passwords, they are more likely to re-type them every time (most ssh clients do not save the password). With a key exchange, they are much more likely to have it fire-and-forget.
Re: (Score:2)
Would be nice if VNC just did the freakin' encryption and screen locking by default and automatically, like Windows Remote Desktop.
Why does Linux stuff always have to be so goddamned hard to use? I swear, Linux coders simply hate end-users, there's no other explanation.
Re: (Score:3, Insightful)
Feeding trolls is always fun, so:
The idea is modularization. VNC does one thing, and does it (sort of) well. SSH does one thing and does it well in version 2. If you can't use SSH authentication in a setting, then you're still able to use VNC with some other auth mechanism. RemoteDesktop is inflexible and monolithic, if one component in the chain is a problem you have to abandon the whole solution. The modularity of *nix is it's strength, but it also makes things more difficult for novices. Windows is there
Terminals mainly? (Score:3, Interesting)
Try conspy [freshmeat.net], very handy utility.
Quick primer (Score:5, Informative)
Here's a quick primer. These are the commands I use all the time. There are a ton more in the man pages or online help.
"screen" to start a new shell under screen
All commands start with CTRL-A, then another key for the command itself. If you really want to send a CTRL-A to your application (Like to go to the beginning of the current line in bash for example, hit CTRL-A twice.)
CTRL-A CTRL-D Detach your current session
"screen -rd" to get back to it
CTRL-A CTRL-C create another "window"
CTRL-A CTRL-N next window
CTRL-A CTRL-P previous window
CTRL-A " see list of current windows
CTRL-A [ Copy mode... you can see the scrollback buffer with this. Esc to exit
CTRL-A ? Help for further stuff.
I run just one instance of screen with multiple "windows." Works beautifully. When you start running more than one screen process under the same user it can make it difficult to re-attach because you have to tell it which pty to attach to.
Nicodemus
Re:Quick primer (Score:5, Insightful)
the day that my grandmother is leaving persistent terminal sessions around is the day I pick up cross-stitching.
It's an advanced thing to do, why would it influence "linux on the desktop (tm)"
Re: (Score:2)
That's what shell scripts are for, no? :)
fpga tools (Score:4, Informative)
The xilinx fpga tools run just fine (perhaps better) from the command line, and have native ports to linux. I believe the same is true for Altera. If you run the xilinx gui tool with the command line log file turned on, it will give you a look at what's required.
IIRC, screen has a pretty detailed man page and has been around a very long time, so should be pretty easy to find examples of setting it up.
For X, usually the real pig is the display server. If you have to run X read up on using the DISPLAY environment variable and just run the X clients on the box and run the server somewhere else - that's what it was made for ;-)
What I read (Score:5, Funny)
"I really want this feature. I've heard of this program that's made for exactly the feature that I want, but I'm unfamiliar with it. HELP ME SLASHDOT YOU'RE MY ONLY HOPE!!1!"
Re: (Score:2)
"There should be a way to send words to another computer about things that I would like to know more about. I bet someone could make a lot of money by inventing a service such as this."
NX (Score:3, Interesting)
Try NX, http://www.nomachine.com/ [nomachine.com]
It's orders of magnitude faster than VNC or native X11, and supports persistent sessions as you describe...
It also runs over SSH, so it benefits from the inherent security of SSH.
I would never even consider using VNC, entirely pointless... slower than native X11.
Re: (Score:2)
In my experience, once you go beyond two systems on the same LAN, vnc copes with the latency much better than native X11. For some reason, swing apps seem to suffer the most (more round-trips baked into how they use X?)
There's also the issue of unreliable links/roaming/etc which are big pluses for vnc/nx.
IMO NX is only marginally better performing than vnc.
Re: (Score:2)
Another vote for NX here. I've been using it for years and VNC doesn't hold a candle.
Also, NX tunnels communications over ssh, so if you're ok punching ssh through the firewall (or already do so), there's no problem.
RTFM! (Score:2)
translation: can someone tell me how to use screen?
let's see, how can i write this so no one will call RTFM on me...
Sun Rays (Score:5, Informative)
Sun make pretty neat thin-client terminals called Sun Ray [sun.com]. Can work with either Linux or Solaris servers.
NB: I'm biased, as I work for Sun.
Re: (Score:2)
Huh.. If all the other posters who read the question as being about purely *text* terminals (despite mention of VNC) are correct, then their suggested answer of "use screen or dtach" are of course much better than using Sunrays. ;)
Re: (Score:3, Interesting)
Uh, the original poster talked about persistent X11 sessions. The Sun Rays are perfect for this. The OP can even have one at home set up to connect to his Sun Ray server at work, detach from the session at the end of the day and reconnect to it from home.
Sun Rays are really one of the coolest technologies to come out of Sun in the last 20 years, but unfortunately, they are such a shift from the norm (and until recently needed Solaris on Sparc for the server) that most companies have no idea of their poten
Re: (Score:2)
I really wish Sun Secure Global Desktop were a free product or had some sort of free edition. It's all the things VNC and FreeNX aren't, and compares well with Remote Desktop and Citrix, but at 100$/seat it's never gonna matter.
why not just use ssh, then the screen utility? (Score:2)
Screen is a great utility. I wrote about it here: http://markwatson.com/blog/2007/04/cant-believe-i-missed-this-unix-utility.html [markwatson.com] and will not repeat myself.
GPU instead of CPU or FPGA? (Score:2)
I also have a genetic algorithm, neural net, artificial life project that needs lots of processing power, after looking at my options (cluster of pc's, cluster of PS3's, FPGA's, GPU's), I found that GPU's look like the best bang for the buck by far.
I've just started the process of converting my critical code to nvidia's C
kdm/gdm with autologin, X, xvnc, ssh and screen (Score:2)
I use the same on my home box. I setup kdm to automatically log my default user in right after startup, and put this
.kde/Autostart/x11vnc /usr/bin/x11vnc -forever -nopw; sleep 10; done) &
s2@fresh:~$ cat
#!/bin/bash
(while true; do
s2@fresh:~$
autostart file in as well, so I have a vnc server listening and sharing that desktop. The vnc port (5900) is firewalled from outside the lan, so it's relatively secure. To access it I use an ssh tunnel, so traffic is encrypted, and when I close my vncviewer window and
Xvfb (Score:3, Interesting)
I use Xvfb to make a virtual screen on the number cruncher (comes with xorg). I don't need to see the display, it just has to be there for wine. If something goes wrong (error box pops up) and there is no progress I take a screen dump of the vortual screen to see it. This eliminates traffic on the network too.
XRDP (Score:2)
XRDP works pretty well. It's basically an RDP "wrapper" for VNC, and should be secure "enough" for your use.
If you need a GUI for the apps, then you need a GUI for the apps. I wouldn't worry much about the overhead since WINE itself will have much more anyway. We're talking here about under 0.5% of your CPU/Memory, which is trivial.
I like it for conveninece since there's no need to install "agents" or specific client-side software. Any Windows box (Post Win2K) has an RDP client, as do most Linux distros
Re: (Score:2)
Windows XP SP3 can't connect to xrdp though. The Windows TS client says "protocol error."
SSL-Explorer (Score:2)
Dont Use Xvnc as a daemon (Score:2)
The easiest way to get a persistent session is to Use the regular vncserver from a SSH command line.
I do it all the time. I suggest you make sure to enable compression and don't go overboard with graphical apps if you access it from the WAN.
Here is where microsoft nailed it - remote desktop (Score:4, Insightful)
Microsoft's remote desktop simply works better than anything in the unix world. Screen is wonderful, but if you want to maintain an entire work session state across several locations, nothing beats RDP.
Why hasn't someone made an X server that uses RDP as the graphics device? Xnest is already 99% of the way there. I'd log in, and if I don't have a session it would create one, if I do have one it would reattach to that one, or maybe give me the option to create a new one.
I could use this in a 100% linux environment using rdesktop to connect to the server (instead of using xdm and Xnest, for instance). It would also work really well in a mixed windows/linux environment because I could use the windows remote desktop client to connect to a linux server and use X programs. Lastly, it would be great for POS applications because 99% of thin client systems already use RDP.
lets get cracking!
Re:Here is where microsoft nailed it - remote desk (Score:5, Interesting)
[quote]Microsoft's remote desktop simply works better than anything in the unix world[/quote]
Sadly, you're not wrong, even though many will refuse to admit it. There's a bit of NIH syndrome going on here and also a general lack of understanding why neither X nor VNC are as functional as Remote Desktop.
Sun's Secure Global Desktop (previously known as SCO Tarantella) actually compares really well in the Unix world, but it's payware even if you need just 1 or 2 seats - functionality that is included with the OS with Remote Desktop. Sun, do all of us, Unix and yourself a favor, and give this product away. Sell licenses to compete with Terminal Server and Citrix, not with Remote Desktop. Pretty please :)
Answer, and a question... (Score:2)
I agree, "screen" is the absolute best answer. I've been using it since the early days, and it's only gotten better (split screens, etc.)
My question: I'd like to be able to list the files in a directory. I've been using "echo *", but it's formatting is a little rough. I've also heard of "ls", but I'm unfamiliar with it. Have other Slashdot users encountered this situation?
(Seriously, though, this seems like a pretty light question to warrant a slashdot article. *Any* semi-experienced Unix admin should b
Re: (Score:2)
Also, the poster indicated he had already heard of screen. An "apt-get install screen" and "man screen" would have answered his question pretty quickly.
(On the other hand, I'm such a big fan of screen, having the word spread on it a bit more is for the common good, I guess...)
modify your bash profile (Score:5, Informative)
Once you're comfortable with screen, which only took me a couple days, back in the mid 90s, add this as the last line of your .bash_profile
exec /usr/bin/screen -xRR
Upon ssh'ing into the box, that'll set up a screen session, or if one currently exists, reattach to it.
Also, if you log in multiple times, from different PCs or whatever, all your logins see the same screen session, which can be convenient if you're "sharing" logins.
To disconnect from the session, just "C-a z" and your ssh connection will drop.
You'll probably want to customize your .screenrc file also. I advise setting
vbell off .... you get the idea ..... ... etc ...
escape ^zz
nonblock on
deflogin off
startup_message off
screen -t procinfo 0 watch -n 60 procinfo
screen -t bash 1
bindkey -k k1 select 1
bindkey -k k2 select 2
bindkey -k k; select 110
bindkey -k F1 select 11
bindkey -k F2 select 12
Oh and set a useful caption line too.
Re: (Score:2)
Err forgot about this.... although it should be pretty obvious.
Good luck running emacs without this line:
escape ^zz
in your screenrc. On the other hand you better read the screen man page and understand what that does before you try it.
Personally, I feel control-A is more useful in emacs, etc, than control-Z. Who needs control-Z when you can just open another screen window with a quick "control-Z c"
I have heard of people remapping the screen control key to other keys but people mostly use the default "a"
Isn't this an ideal case for EC2? (Score:2)
VNC is a "waste"??? (Score:3, Insightful)
I've used VNC routinely for this kind of purpose for years -- in fact, I do almost all my programming work using it. I have not found it to be a resource hog by any means. Just checking some of my VNC sessions now, resident memory use by the Xvnc process seems to stay between 20 and 60MB. At current memory prices, this is pretty much negligible (and I would assume you have plenty of DRAM on your compute box -- 8GB at least, yes?).
Others have mentioned SSH tunnelling -- I can assure you this is reliable; I've used it day in and day out for years.
Use Screen if you want, but personally I wouldn't even think twice about using VNC.
Shouldn't this be mandatory knowledge? (Score:2)
Wow.. a decade ago knowing about screen would have been pretty common and necessary knowledge. Now we have to Ask Slashdot for instructions for using it?
It seems like we've some how failed in the Linux community to instill this knowledge. Even worse, Soulskill felt that it was important enough to warrant posting to Ask Slashdot.
Don't get me wrong - I don't think we need another tutorial. In fact, quite the opposite. I bet if you put "screen tutorial" into Google it'll come up with tens of thousands of m
Get familiar with SCREEN (Score:2)
Screen is designed for exactly what you are wanting. I wouldn't look at anything else.
It's easy to use, takes about 5 minutes to figure out how to use it.
REALLY old-school and local for text apps (Score:2)
Run getty on a serial port with no hardware flow control. Run a terminal emulator on a laptop. Use a null-modem cable to connect. Unplug when you are done and the session continues to run. Security is either great or it sucks, depending on your situation, because physical access is necessary and sufficient. Very old-school, but cheap and easy. Run screen if you need multiple sessions. Text-only, though.
Screen if you are going with text-terminal. (Score:2)
It's 100% exactly what you are asking for. So exact, in fact, that I wonder why somebody didn't just answer you before this even became a story.