Void's Forums

by **dishawjp** » Sat Nov 20, 2004 7:04 pm

su - username also did nothing.

Code: Select all: [dishawjp@eunix ~]$ su - dishawjp Password: [dishawjp@eunix ~]$

by **Void Main** » Sat Nov 20, 2004 7:08 pm

Do me a favor and check the date/time stamp on your /etc/profile. Make a backup copy of your /etc/profile (cp -a /etc/profile /etc/profile.bak). Edit your /etc/profile and put in a couple of echo statements to see if the error happens before the profile is loaded, after, or somewhere in the profile. I would add an "echo TEST1" to the beginning and "echo TEST2" to the end and then log in on one of your VCs and see which message shows up where.

by **dishawjp** » Sat Nov 20, 2004 7:24 pm

OK, here we go. First, the date and time of my /etc/profile:

Code: Select all: -rw-r--r-- 1 root root 842 May 24 17:38 profile

then I copied my /etc/profile to /etc/profile.bak

Then I edited my /etc/profile to add some echo statements as you suggested:

Code: Select all: [root@eunix etc]# vi /etc/profile [root@eunix etc]# more /etc/profile # /etc/profile # System wide environment and startup programs, for login setup # Functions and aliases go in /etc/bashrc echo Test1 pathmunge () { if ! echo $PATH | /bin/egrep -q "(^|:)$1($|:)" ; then if [ "$2" = "after" ] ; then PATH=$PATH:$1 else PATH=$1:$PATH fi fi } # Path manipulation if [ `id -u` = 0 ]; then pathmunge /sbin pathmunge /usr/sbin pathmunge /usr/local/sbin fi pathmunge /usr/X11R6/bin after # No core files by default ulimit -S -c 0 > /dev/null 2>&1 USER="`id -un`" LOGNAME=$USER MAIL="/var/spool/mail/$USER" HOSTNAME=`/bin/hostname` HISTSIZE=1000 if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then INPUTRC=/etc/inputrc fi export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC for i in /etc/profile.d/*.sh ; do if [ -r "$i" ]; then . $i fi done unset i unset pathmunge echo test2 [root@eunix etc]#

And I got this when I logged into a virtual terminal, right after I logged in:

Code: Select all: Test1 KDSKBENT: Invalid argument failed to bind key 255 to value 2639 test2

by **Void Main** » Sat Nov 20, 2004 7:28 pm

Ok, that means that the error is coming from a command that is called from the /etc/profile. Add some more echo statements in until you narrow it down to the exact line.

by **dishawjp** » Sat Nov 20, 2004 7:35 pm

OK, I inserted some more "echo testx" lines. It now looks like this:

Code: Select all: [root@eunix etc]# vi profile [root@eunix etc]# cat profile # /etc/profile # System wide environment and startup programs, for login setup # Functions and aliases go in /etc/bashrc echo Test1 pathmunge () { if ! echo $PATH | /bin/egrep -q "(^|:)$1($|:)" ; then if [ "$2" = "after" ] ; then PATH=$PATH:$1 else PATH=$1:$PATH fi fi } echo test3 # Path manipulation if [ `id -u` = 0 ]; then pathmunge /sbin pathmunge /usr/sbin pathmunge /usr/local/sbin fi echo test4 pathmunge /usr/X11R6/bin after # No core files by default ulimit -S -c 0 > /dev/null 2>&1 USER="`id -un`" LOGNAME=$USER MAIL="/var/spool/mail/$USER" HOSTNAME=`/bin/hostname` HISTSIZE=1000 echo test5 if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then INPUTRC=/etc/inputrc fi export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC for i in /etc/profile.d/*.sh ; do if [ -r "$i" ]; then . $i fi done echo test6 unset i unset pathmunge echo test2 [root@eunix etc]#

The error came in between "test5" and "test6"

by **Void Main** » Sat Nov 20, 2004 7:39 pm

So that means it's in one of the scripts that get sourced that reside in the /etc/profile.d. Check the dates on the files and see if any of them were added or modified in the last day or two, if so add some debugging statements to those, if not add some debugging statements to all of them. You may or may not want to back them up first. You can restore your original /etc/profile at this point (cp -a /etc/profile.bak /etc/profile).

by **dishawjp** » Sat Nov 20, 2004 7:41 pm

In anticipation of your next question, I inserted another test, test7, right here:

Code: Select all: echo test5 if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then INPUTRC=/etc/inputrc fi echo test7 export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC for i in /etc/profile.d/*.sh ; do if [ -r "$i" ]; then . $i fi done echo test6

and when logging in to a virtual terminal, the error came in between test7 and test6

by **dishawjp** » Sat Nov 20, 2004 7:44 pm

To hone in a little closer, I just put a test8 in.

Code: Select all: echo test7 export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC echo test8 for i in /etc/profile.d/*.sh ; do if [ -r "$i" ]; then . $i fi done echo test6

and the error came in between test8 and test6

by **Void Main** » Sat Nov 20, 2004 7:46 pm

Aha, that was *almost* my next question but I already knew the answer to that question so I skipped that one and moved to the next one. Read my last post. :)

by **dishawjp** » Sat Nov 20, 2004 7:56 pm

We're thinking a bit alike, it's just that you're a lot faster than I am. I checked the files in the profile.d and none have been messed with recently. Not since I installed on the 13th.

Code: Select all: [root@eunix profile.d]# ls -clt total 152 -rwxr-xr-x 1 root root 78 Nov 13 16:42 kde.csh -rwxr-xr-x 1 root root 74 Nov 13 16:42 kde.sh -rwxr-xr-x 1 root root 2182 Nov 13 16:40 lang.csh -rwxr-xr-x 1 root root 2470 Nov 13 16:40 lang.sh -rwxr-xr-x 1 root root 51 Nov 13 16:10 mc.csh -rwxr-xr-x 1 root root 45 Nov 13 16:10 mc.sh -rwxr-xr-x 1 root root 218 Nov 13 16:06 krb5.csh -rwxr-xr-x 1 root root 210 Nov 13 16:06 krb5.sh -rwxr-xr-x 1 root root 58 Nov 13 15:58 gnome-ssh-askpass.csh -rwxr-xr-x 1 root root 70 Nov 13 15:58 gnome-ssh-askpass.sh -rwxr-xr-x 1 root root 170 Nov 13 15:54 which-2.sh -rwxr-xr-x 1 root root 13 Nov 13 15:54 vim.csh -rwxr-xr-x 1 root root 181 Nov 13 15:54 vim.sh -rwxr-xr-x 1 root root 720 Nov 13 15:48 colorls.csh -rwxr-xr-x 1 root root 713 Nov 13 15:48 colorls.sh -rwxr-xr-x 1 root root 122 Nov 13 15:48 less.csh -rwxr-xr-x 1 root root 108 Nov 13 15:48 less.sh -rwxr-xr-x 1 root root 192 Nov 13 15:47 glib2.csh -rwxr-xr-x 1 root root 190 Nov 13 15:47 glib2.sh [root@eunix profile.d]#

So now I'm REALLY confused!

by **Void Main** » Sat Nov 20, 2004 7:59 pm

Yes, but the error is still coming from one of them. Put an echo in each one, with each file's name:

echo filename

by **dishawjp** » Sat Nov 20, 2004 8:02 pm

Will do. I'm only going to mess with the .sh files and leave teh .csh files since I'm running bash. I really don't know where to put the echo statement, so for now I'll just put it in the beginning of the script.

If this is wrong, just let me know.

by **Void Main** » Sat Nov 20, 2004 8:04 pm

That's good enough to pin it down to which script it's in, then do like you did with profile on that one script.

by **dishawjp** » Sat Nov 20, 2004 8:11 pm

It looks like the error is in lang.sh. It appeared right after lang.sh and before less.sh.

My luck, it has to be the longest script

by **Void Main** » Sat Nov 20, 2004 8:18 pm

Heh heh, well that script is part of the "initscripts" package which was one of the ones that you upgraded. I'm running v7.93.5-1 which is the version you just upgraded to. That has to be where the problem cropped up in though (at least for the 1st of your 2 errors).

Void's Forums

KDSKBENT, eggcups and gnome volume manager errors!

Who is online