I've got a problem that started recently on a RHEL 6.4 (kernel 2.6.32-358.14.1) workstation where if someone logs out of their session on the console, instead of returning to user login the sc... [by danfour]
I have vino running on Fedora 20, sharing the console. This works, however the resoution is way too large. What config file must be created or edited to set the console resolution in vnc to 1280x1024 matching the actual installed console? Bonus points if you can tell me the config contents to do this! This is vino sharing the console, not a session started by a user as a new login session.
At my work I'm faced with a challenge. It has been decided that we're moving to a Linux desktop environment. Basically it's a cluster of RedHat Enterprise Virtualisation (RHEV) servers running VDI's for all our users. They can then connect to the console of a running VDI and start working.
Now all that is working fine, but there is still one challenge left.
I've got jetty set up to boot on login using the standard init script in CentOS 6.3 - my problem is that it decides to log a few messages to the console before redirecting it to it's own log files, which ends up printing out on the login screen.
It ends up with:
login: 20120-07-13 19:53:09.039:INFO::Redirecting stderr/stdout to /opt/jetty/logs/2012_07_13.stderrout.log
I am having a problem that has been popping up recently (past few weeks), where my login attempts through putty would timeout. Going into VMware, my attempt to login through console, with a local admin account, were also timing out. Since I was unable to access the VM, I decided to reboot the server and both login methods were restored. A day or two later, the problem had returned.
Hopefully my question makes sense, but I was wondering if the telnet service has anything to do with console logins or if they are completely unrelated. So for example, does the /etc/default/login file in UNIX have anything to do with Telnet?
Using the defaukt x86_64 kernel openSuSE 11.2 (uograded from 11.1) works fine.
I have compiled my own kernel using the 11.1 config with minor changes. Botting runs fine and looking at the boot.msg compared between the default and my own kernel I only see preloadtrace.ko module missing on my own kernel which I would not expect causing mthe problem.
Well the system is up-to-date, apart from a downgraded kernel (3.4.9) because of problems with usb ethernet adapter drivers (I am guessing this should not be an issue, but can try with the newest kernel to eliminate this).The setup is very basic. There is no display manager, automatic login to virtual console was set up like described in the wiki . Then startx is used to run dwm.