Am Dienstag, 4. März 2003 00:05 schrieb Eric Carbone:
No sarcasm intended ...
Sorry... <arrrgh> tried... but... <rrrrgh> couldn't resist... *bg*
if I cd to /root and type ls -l I see this:
.DCOPserver_myserver -> /root/.DCOPserver_myserver_:0
If I try to edit the file I get: Bash: ./.DCOPserver_myserver: No such file or directory Press any key to continue
Well if /root/.DCOPserver_myserver is a symlink to /root/.DCOPserver_myserver_:0 and /root/.DCOPserver_myserver_:0 does not exist, then you have found the problem.
Delete the broken symlink, I think the missing file and the broken (and now deleted) symlink should be created again when restarting X.
Daniel
Being a linux novice, I was afraid to start arbitrarily deleting files ;-) I will try deleting this sym link and hope that linux 'fixes itself' when I reboot. Thanks for your help. I'll cross my fingers and ask my client to try logging in again.
On Monday 03 March 2003 03:27 pm, Eric Carbone wrote: ---------snip----------
Being a linux novice, I was afraid to start arbitrarily deleting files ;-)
I will try deleting this sym link and hope that linux 'fixes itself' when I reboot.
Except when I'm moving to fast for my own good (last night) I usually rename rather than delete, once I'm sure things are working I go back and get rid of the unnescessary junk. Just a thought. BTW getting rid of the mcop and dcop files in the home directory often seems to be the solution to the symptoms you mentioned good luck -- dh Don't shop at GoogleGear.com!
Am Dienstag, 4. März 2003 04:03 schrieb David Herman:
Except when I'm moving to fast for my own good (last night) I usually rename rather than delete, once I'm sure things are working I go back and get rid of the unnescessary junk.
Just a thought.
Well, this does make sense to files. But backing up a broken symlink is rather senseless in my eyes. Daniel
participants (3)
-
Daniel Eckl
-
David Herman
-
Eric Carbone