Wolfgang Slany <wsi@dbai.tuwien.ac.at> writes:
After upgrading to suse 8.0 I had a strange problem with canna (which had worked before, and which I eventually could resolve): canna seemed not to work anymore, xemacs etc reporting that it couldn't connect to the canna server and:
[...]
What seemed to have helped finally on June 12 was to insert "unix" into the /etc/hosts file somewhere together with localhost.
Yes, both "localhost" and "unix" are necessary to give the host running the canna server access to its own canna server, only one of them is not sufficient! If you have a non-empty /etc/hosts.canna file, it should contain at least the lines localhost unix to give the host running the canna server access.
It then worked fine for nearly a month, until suddenly, on July 7, canna again stopped working with the same symptoms as before (strangely enough as I did not change whatsoever on the system since I made that change in /etc/hosts).
Today, I removed /etc/hosts.canna (which contained nothing other than localhost and unix in separate lines) and it worked again.
I guess you had a space behind either "localhost" or "unix". This is already enough to prevent access. Canna is *very* picky about the syntax of /etc/hosts.canna.
I assume this is no security risk as all ports from outside are closed and the system is standalone
Yes, in that case you can safely delete /etc/hosts.canna.
(see http://www.suse.de/~mfabian/suse-cjk/canna-access-control.html for details).
I have improved that description now to make it more clear that both "localhost" and "unix" are needed and that you should not add any extra spaces. Probably I should patch Canna to ignore at least the spaces when reading /etc/hosts.canna. -- Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。