You are not logged in.
i, I just updated and besides what appears to be the "chromium" problem when I ran an install from the AUR I got "ssh: Could not resolve hostname 192.168.1./root/.xinitrc Name or service not known. Further when I rebooted I got through the post entered 'xinit ' and got the same message after being kicked back to console. The further added statement of "xinit connection to server lost" I have no idea what this is. Is anyone else experiencing this? I upgraded my XFCE and didn't have this problem, but it doesn't have a lot from the AUR. The install in question is Awesome my main DE and it uses quite a bit from the AUR. That is the biggest defining difference the initial base install is exactly the same.
thanks in advance for your help.
--jerry
Last edited by jk121960 (2012-04-07 12:02:07)
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
Check your hostname.
Offline
yea I did, I checked hostname, hosts etc, nothing out of place.
thanks
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
What are the exact contents of your ~/.xinitrc file? Does the issue also occur if you only leave you awesome launch line in there?
Burninate!
Offline
What are the exact contents of your ~/.xinitrc file? Does the issue also occur if you only leave you awesome launch line in there?
yes it happens either way and it just started after the new updates today, I restored and updated again to see if something got foobarred but it happened again exactly the same so it is deffinately something that gets updated.
thanks for your help
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
# exec ck-launch-session
#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
#rox -b Default -p default
exec ck-launch-session dbus-launch awesome
sleep 2
#nitrogen --restore &
#cairo-compmgr & Arch Awesome, Ranger & Vim the coding triple threat.
Offline
Ok we figured out what it was, I had created a script for connection ssh to a arbitrary server on my local net work 192.168.1.0, I named this script 'sh' and put it in the /usr/bin directory. For some odd reason this script is being called during boot. Anyone know why that is? by removing it or changing the script name everything cam back to normal. I someone knows why this is being called I would be grateful to know. I checked for other files names 'sh' and there was none.
if you know please help me to understand thanks
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
I someone knows why this is being called I would be grateful to know. I checked for other files names 'sh' and there was none.
$ which sh
/bin/shOffline
That just made my day :-)
Offline
Ok Karol I'm a dope please explain why. what does /bin/sh get used for?
thanks
-jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
OK I get it, it didn't ring when I looked at but I found the man page. Ok it was early like 3 in the morning, I was brain dead.
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
Aaaaand what does 'man sh' say?
http://en.wikipedia.org/wiki/Bourne_shell
Edit: Glad you've found it yourself :-)
Last edited by karol (2012-04-07 12:03:01)
Offline
My Humble Apologies Sensei. ![]()
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
jk121960
Don't feel bad.
In my first UNIX job, I was writing a script in my user account, and had to use the 'test' utility to test a condition. It was only a few lines, just to test something out. I didn't know what to call it, so i just named it, oh, yes, "test".
I'll bet some of you know what's coming.
I ran it, and expected to get some quick output, but I got nothing. Not even a shell prompt. I ctrl-c'ed, and managed to do an ls, which said "out of process ids". Yup. I managed to cover /bin/test with my own script. So every time my script hit the test condition, it invoked another copy of itself. ALL the way down....
I couldn't do anything from my terminal, so I ran to the ops room, where they had a hardcopy ops console. A 'ps' showed more "tests" than you could imagine. I figured if I could kill from somewhere near the top, that might work, but no luck. Because all the way down at the bottom of the recursion was a copy of my 'test', just waiting for a process id. So every time I killed one, he gobbled it up.
I'm sure there was some other way out, but I didn't know how. So I had to reboot. Luckily, it was after hours, and no one ever said anything to me about it.
I had the root at this place. Yeah, they actually gave me the root.
Offline
Yes I think I know how you feel and thanks for the post if nothing else to let me know that sh**t happens and sometimes you just don't see what right in front of you.
thanks again
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline