I just wonder if tty10 in Linux is dedicated for printing debug informations.
When I type CTRL-ALT-F10 I got some informations coming straight from** /var/log/messages** the 12 last lines.
Sep 9 19:28:23 antares kernel: 36.562840] bridge-eth0: attached
Sep 9 19:28:23 antares /usr/sbin/cron[3498]: (CRON) bad username (/etc/cron.d/smolt)
Sep 9 19:28:23 antares /usr/sbin/cron[3498]: (CRON) INFO (running with inotify support)
Sep 9 19:28:24 antares vmnet-detect[3586]: NetDetectDaemonInit: No host policy file found. Not initializing filter.
Sep 9 19:28:24 antares vmnet-detect[3586]: Unable to initialize the daemon
Sep 9 19:28:25 antares SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Sep 9 19:28:25 antares SuSEfirewall2: using default zone 'ext' for interface eth1
Sep 9 19:28:25 antares kernel: 38.388746] start_kdeinit (3789): /proc/3789/oom_adj is deprecated, please use /proc/3789/oom_score_adj instead.
Sep 9 19:28:25 antares SuSEfirewall2: Firewall rules successfully set
Sep 9 19:28:27 antares kernel: 40.866093] EXT4-fs (sdd1): re-mounted. Opts: acl,user_xattr,commit=0
Sep 9 19:28:40 antares kernel: 53.071110] ALSA pcm_lib.c:323: BUG: pcmC0D0c:0, pos = 5461, buffer size = 5461, period size = 2730
Sep 9 19:28:40 antares pulseaudio[4153]: pid.c: Daemon already running.
I ask you this because the tty10 in /dev is set to read only and all the others are set to write only.
And when I wake my computer from “hibernation” I got a message telling each minute that there is an I/O error on tty10.
How can I set rw permissions on tty at boot ? Is that recommended or not ?
In the negative, how come the “hibernation” cause this to happen ? I never had such issue before the last update of the system.
I did not test with sleep I never need to put my computer to sleep. But hibernation was often used since the last update.
Thank you in advance for any advices or enlighments ^^
That is the point, now I have to find first the reason why the tty is set to read only and second how I can fix the issue.
I have no idea to tell the system to set tty10 in write only for group. In my configuration, I haven’t been precise, the read only was set for the group, for the user I got character read and write (crw).
The owner and owner group are root:root (??)
(I volontary deleted the ttyzzz that I really don’t care, the regular expressions are not my strength in shell)
Still digging and I feel a sensive slowness of the responsivness of the kde environment since last update, but this will be the subject of another thread…
I am not quite sure hat your problem is. I have also messages at* tty10*, I never looked there, thus I saw this for the first time after seeing this thread. But Why should it be a problem?
What is a bit strange is the access bits, I have no explanation for it, but again, what is the problem?
And removing device special files (or anything) from within */dev *is futile. It is created dynamicaly and all will be there again after next boot. When you realy hate them (again, why?) you should create udev rules to prevent their creation.
PS, In the end of the expression in the grep command you have* $. The*$* is useless because ** *allready means “whatever string” and that includes all characters until the end of the line.
I’m not fluent with regular expressions ^^ I was trying to say “no or one digit that may be 0” ^^
The problem is that recently, since last update, when I wake up from “hibernation” I have a I/O error from a process that is tty10 (the pid returned by syslog-ng matches).
The message is logged in the var/log/message file every minute and that is anoying…
That’s why I’m trying to find a way to change the read only flag on tty10 or find a way to use hibernation again as “before”. Since I saw this issue I stopped using the hibernation feature.
Still have no clues… I can use bash.bashrc to change the permissions on tty10 but it sucks… there is a better way I guess.