View previous topic :: View next topic |
Author |
Message |
MorbidDK n00b
Joined: 13 Feb 2003 Posts: 48
|
Posted: Tue Jun 17, 2003 6:51 pm Post subject: etc-update errors |
|
|
I have noticed recently that whenever I run /usr/sbin/etc-update I get the following error:
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
The configs get updated properly, just this error presents itself and I'm unsure as to where its coming from. Anyone able to help out with this? |
|
Back to top |
|
|
rosowski n00b
Joined: 09 Nov 2003 Posts: 51
|
Posted: Mon Jan 12, 2004 7:13 pm Post subject: |
|
|
I'm getting the same error running kernel 2.6.0.
It started after I emerged vmware and after that ran etc-update. Now I even get it, when opening any man page. |
|
Back to top |
|
|
thc013 n00b
Joined: 30 Dec 2003 Posts: 18
|
Posted: Tue Jan 13, 2004 1:12 pm Post subject: |
|
|
get also the same error
and get the error with the install after kernel wanted to add hotplug and then get the same error
but getcwd is saying that it can't open a database in /usr/lib/slocate/slocate.db is empty |
|
Back to top |
|
|
thc013 n00b
Joined: 30 Dec 2003 Posts: 18
|
Posted: Tue Jan 13, 2004 1:31 pm Post subject: |
|
|
think it had something to do with etc-update
when you have to do that it asked -1 or -3 or -5 option i think i made the mistake to choose -3 instead of -5 but it is a gues |
|
Back to top |
|
|
pipplo n00b
Joined: 21 Mar 2004 Posts: 11
|
Posted: Fri Apr 23, 2004 5:04 pm Post subject: |
|
|
any ideas on how to fix this? I'm having the same problem now... |
|
Back to top |
|
|
Daeluin n00b
Joined: 04 Jan 2003 Posts: 57 Location: lost
|
Posted: Mon Apr 26, 2004 5:57 pm Post subject: |
|
|
noticed the same thing this morning.
couldn't think of anything I'd done that might've caused this. first noticed with qmailctl commands, then rc init commands, and etc-update. did an emerge sync and no difference.
then after spacing out for a few minutes I did 'ls' in a dir and got nothing. that seemed odd, so I went up a dir, 'ls' - it worked; back to original dir. now 'ls' works. then I noticed the getcwd errors had stopped...
guess something snapped back into place. .. |
|
Back to top |
|
|
Hinkey n00b
Joined: 28 May 2003 Posts: 5
|
Posted: Wed Apr 28, 2004 5:17 pm Post subject: fix |
|
|
this problem seems to fix itself if you ls, then cd .., then ls, then cd .., continueing untill you no longer get the error... not sure of the cause or what the actualy problem is but that also fixed it for me _________________ -=Hinkey=- |
|
Back to top |
|
|
MadDog n00b
Joined: 05 Dec 2002 Posts: 10 Location: Maribor, Slovenia
|
Posted: Tue May 04, 2004 4:28 pm Post subject: |
|
|
funny, i got this message not only with etc-update, but also when running init.d scripts ... The "ls" "cd .." trick worked for me tho |
|
Back to top |
|
|
SecMon n00b
Joined: 01 Apr 2003 Posts: 12 Location: California
|
Posted: Sun Jun 27, 2004 9:46 pm Post subject: |
|
|
This will happen if you deleted the directory you are in from a different login or shell (screen). Be careful of cutting tree limbs you are standing on. |
|
Back to top |
|
|
zie Tux's lil' helper
Joined: 26 Sep 2003 Posts: 126
|
Posted: Mon Aug 02, 2004 1:52 am Post subject: |
|
|
Ah.. i see. it makes sense now _________________ /etc/init.d/alsasound start
* ALSA driver is already running.
/etc/init.d/alsasound stop
* ERROR: "alsasound" has not yet been started. |
|
Back to top |
|
|
ugus Apprentice
Joined: 23 Jul 2004 Posts: 213 Location: Darmstadt, Germany
|
Posted: Sun Jan 23, 2005 11:13 am Post subject: |
|
|
i got also this morning the same failure as i run any commands, even after typing su.
But if i become root with su - root command rather then only su , then i don't get any failure message _________________ while(!sleep())
{
sheep++;
}
My Desktop |
|
Back to top |
|
|
ugus Apprentice
Joined: 23 Jul 2004 Posts: 213 Location: Darmstadt, Germany
|
Posted: Sun Jan 23, 2005 11:15 am Post subject: |
|
|
MadDog wrote: | funny, i got this message not only with etc-update, but also when running init.d scripts ... The "ls" "cd .." trick worked for me tho |
worked for me to _________________ while(!sleep())
{
sheep++;
}
My Desktop |
|
Back to top |
|
|
pixelcatcher n00b
Joined: 31 Jan 2004 Posts: 60 Location: Stuttgart
|
Posted: Thu Jul 21, 2005 6:28 pm Post subject: |
|
|
for me, too - weird _________________ www.pixelcatcher.de |
|
Back to top |
|
|
KristyX Apprentice
Joined: 18 Dec 2003 Posts: 206 Location: Malaysia
|
Posted: Tue Nov 22, 2005 5:54 am Post subject: Re: fix |
|
|
Hinkey wrote: | this problem seems to fix itself if you ls, then cd .., then ls, then cd .., continueing untill you no longer get the error... not sure of the cause or what the actualy problem is but that also fixed it for me |
worked for me as well.. and yes, i think i deleted the directory i was in _________________ Knowledge is a process of piling up facts; wisdom lies in their simplification. [Martin Fischer] |
|
Back to top |
|
|
chovy Guru
Joined: 03 Dec 2004 Posts: 453
|
Posted: Sun Dec 11, 2005 11:54 am Post subject: |
|
|
i'm seeing the same errors too.
I don't think I've done anything recently to mess up my filesystem. I use screen quite a bit, so maybe I removed a directory from a different login while the old 'screen' process was still loaded.
The problem seems intermittent, so I can't be sure if exiting screen has fixed the problem or not. _________________ Woof, Woof! Add "[solved]" to the title! Woof, Woof! |
|
Back to top |
|
|
|