Gerard wrote:
> Melchior wrote:
> > Yes, and I was right: this file just doesn't exist! This is not an
> > fgfs message, but one of the operating system.
>
> Not so Quick......
> Oh do you remember i told you :
You can't really argue with a syscall result. The file isn't there.
Maybe there are some other conditions (lack of x permissions in a
directory on the path?) that will produce an ENOENT instead of an
EPERM, so it's not impossible that the file is present. But the
bottom line is that fgfs can't read the file. We can't debug this for
you; you need to figure out your system configuration first.
Try, as the user running fgfs, things like:
ls -l /home/tux-le-boss/.fgfs/preferences.xml
cat /home/tux-le-boss/.fgfs/preferences.xml > /dev/null
more /home/tux-le-boss/.fgfs/preferences.xml
You will eventually discover what the problem is. Again, the syscall
result is telling: you can argue on the mailing list until you
collapse from exhaustion and you will never convince the OS that the
file is there. :)
Andy
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
