Annoying/Odd syslog messages

[wesmoc]

I'm seeing a lot of the following messages in the "dmesg" output:

shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0

The error itself doesn't look all that good (kinda makes me think something is failing). Of course, it is just enough information to concern me, but not enough to give me any clue as to what it might be. Ugh.

Anyone seeing similiar stuff? I've been seeing it since I originally upgraded my TiVo, but I never bothered to look in to it (the TiVo itself is running fine).

The only reason I started questioning it is that I have noticed that NCID seems to stop working every so often, and the only way to get it working again is to kill -TERM the process, wait a few moments, then start it up again. And, while trying to debug that issue, I couldn't get past those dmesg/syslog messages.

[ocntscha]

I'm seeing a lot of the following messages in the "dmesg" output:

shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
1 1 0 0
- 0 1 0 0

The error itself doesn't look all that good (kinda makes me think something is failing). Of course, it is just enough information to concern me, but not enough to give me any clue as to what it might be. Ugh.

Anyone seeing similiar stuff? I've been seeing it since I originally upgraded my TiVo, but I never bothered to look in to it (the TiVo itself is running fine).

The only reason I started questioning it is that I have noticed that NCID seems to stop working every so often, and the only way to get it working again is to kill -TERM the process, wait a few moments, then start it up again. And, while trying to debug that issue, I couldn't get past those dmesg/syslog messages.Just speaking in a very broad sense here not really from anything I know about Tivos but just general UNIX/Linux point of view, that looks to me like the type of error you might see if some program where using a particular directory in some fashion, like writing a log file maybe, but then the directory the program was using and still is trying use has unexpectedly vanished since the program was first started.

[ocntscha]

The error can be recreated like so..

root@tivo:~ bash# cd /var/tmp

root@tivo:/var/tmp bash# mkdir -p foo/bar

root@tivo:/var/tmp bash# cd foo/bar

root@tivo:/var/tmp/foo/bar bash# pwd
/var/tmp/foo/bar

root@tivo:/var/tmp/foo/bar bash# rm -r /var/tmp/foo

root@tivo:/var/tmp/foo/bar bash# cd ..
cd: could not get current directory: getcwd: cannot access parent directories: N
o such file or directory
cd: could not get current directory: getcwd: cannot access parent directories: N
o such file or directory

root@tivo:. bash#

[ocntscha]

Still thinking about. See if you have a file on your Tivo named shell-init, and if its a script see what it is and what it does.

find / -name shell-init (I checked, I don't have that on my Tivo)

[wesmoc]

Well, did the find.. no results, as expected.

I assumed that the "shell-init" part was due to something firing off from a parent application which required a shell of sorts (and, hence, "init"ializing a new "shell").

Unfortunately, I have little else to go on since the output is so limited.

Whatever it is, it is rather persistent. Reboots of the Tivo don't seem to stop it. :(

[ocntscha]

Ok, a little Googling and I've got a guess at it for you. I'm guessing the directory that was the current directory when tnlited was started has since been deleted and if you pay close attention you'll find that error message is generated once for each time you log in over telnet.