Hot answers tagged console
There is a "secret" keyboard shortcut to force an exit :~) From the frozen session, hit these keys in order: Enter~. The tilde (only after a newline) is recognized as an escape sequence by the ssh client, and the period tells the client to terminate it's business without further ado. The long-hang behavior on communication issues is not a bug, the SSH ...
You can look at the $STY variable. If it is not "" then you are in a screen session. I am in screen $ echo $STY 29624.pts-1.iain-10-04 $ I am not in screen $ echo $STY $
This is similar to what happens when you delete a file that another system has open on a NFS mount. The problem is that the file has been removed from the filesystem while its "link count" was >1, meaning that other processes are still holding it open. Log in to the system where the file physically resides. (no network mount) Execute lsof ...
While I am on windows I use putty.
Holding down the Ctrl-Alt while dragging the left mouse button.
@ signifies that the file has extended attributes. Those attributes are usually used to signify that the file came from a package, was downloaded from the internet, etc. ls -al@ imap.a will show you the extended attributes that are saved for that file.
The console-tools package allows console options to be controlled. To turn off screen blanking and powerdown, set BLANK_TIME and POWERDOWN_TIME to 0 in /etc/console-tools/config. If you'd prefer not to modify the config file, the same effect can be achieved by creating a new file in /etc/console-tools/config.d containing the following: BLANK_TIME=0 ...
This worked for me: ssh -n user@hostname1 'tail -f /mylogs/log' & ssh -n user@hostname2 'tail -f /mylogs/log' &
You can look at the $TERM variable. echo $TERM If it's a screen session, the term variable should return "screen". root@deore:/volumes# echo $TERM screen Ctrl-a -d (to exit screen) root@deore:/volumes# echo $TERM xterm Also check: http://stackoverflow.com/questions/3472287/how-do-you-tell-if-the-current-terminal-session-is-in-gnu-screen
Or you use /etc/kbd/config to set up (depends on your system, what is installed) BLANK_TIME=0 BLANK_DPMS=off
Terminal.app when using Mac OS X
gnu screen, hands down.
In ESXi 5 (and 4.1), this is referred to as "Tech Support Mode." It's an explicit option in the ESXi console interface. See the following article from VMWare on how to enter it.
The parameter is controlled via the kernel command line, using setterm merely alters the runtime settings. To disable it system wide you can alter your kernel boot command line by appending it with "consoleblank=0" in your boot configuration (grub/lilo). If something during boot setterm's it then it will override the value.
You should check out Windows Powershell. http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx You could also try Cygwin if you're partial to Linux. http://www.cygwin.com/
My preferred option is to go with multitail. I'd run something like: multitail -l 'ssh user@host1 "tail -f /some/log/file"' -l 'ssh user@host2 "tail -f /some/log/file"'
This can happen after a program dies leaving a terminal in an abnormal state. To fix it temporary you "reset" the terminal with: $ reset
You could try using the "screen" command. This will allow you to run a multiuser session which 2 users can connect and share. First you'll need to set the suid bit. screen comes with it turned off, and it is necessary for multiuser mode: sudo chmod +s /usr/bin/screen sudo chmod 755 /var/run/screen The first user connect, running screen -S shared The ...
I believe that return code is a generic .NET console app crashed code. The way the job is set up in Task Scheduler is not causing this issue. Check the Application event log on the server for any errors that occurred near the time the job 'completed'. Those events should give you more information as to why the job exited abnormally, so you have some idea ...
. is the current directory. So the command is telling the shell to look for the executable in the current directory. Do not confuse with . foo, which is a completely different command.
Wen you run a command without any prefix then Unix systems look up the command within PATH. For example if you type ls then Unix will walk all paths listed in PATH to find the ls binary. For example let's assume your PATH is set to /bin:/usr/bin:/usr/local/bin then just typing ls will make your shell find the command at /bin/ls and execute it. Unix systems ...
iTerm on OS X. http://iterm.sourceforge.net/
Many network devices use the Yost RJ45 pinout for RS-232 console communications. Cisco is probably the best known, but certainly not the only. The switch should have come with a DB9 to RJ45 blue cable. You can just pickup any USB-DB9 Serial adapter (though I highly recommend getting one with a Prolific PL2303HX Rev D Chipset, as they "just work" and are ...
If your server has a serial port you can connect through it easily enough. Let us assume the simplest case; 1 server and a cart pc or laptop. Add an entry to your /etc/inittab file similar to: s0:12345:respawn:/sbin/agetty 19200 ttyS0 vt100 That will tell the server to listen on ttyS0, the first serial port, for terminal like behavior. Plug a cable ...
I'm using multitail to monitor logs, it includes coloring as well as multiple logfile monitoring either merged or in windows. Give it a try.
Any reason why you can't use something like this: tail -f FILE | grep --color=always KEYWORD source: commandlinefu.com
Unless you have changed the default key bindings, you can do Ctrl-a Ctrl-t, which will show the time, if you are in screen. This will work even if you have ssh:d away somewhere else, unlike the other suggestions.
Most of the information you want will be in /var/log/dmesg and /var/log/messages after the system boots, you should check those files first. Generally linux machines run mingetty for the virtual terminals. If you have a traditional sysv init system, those are controlled by /etc/inittab. You can add the --noclear option to mingetty to prevent clearing the ...
Whereas an SSH connection transmits keystrokes, an HP ILO connection transmits key states. Each time you press a key, the server receives separate KeyDown and KeyUp events. The repeated keystrokes result when the KeyUp event is received late. The two most likely reasons for the KeyUp event to be received late are: Network congestion/performance issues. ...
Only top voted, non community-wiki answers of a minimum length are eligible