Comment 20 for bug 318689

Am Fr, 6. März 2009 09:49:46 schrieb Sebastien Bacher:
> > - still uses hardcoded obsolete values of bogus logfiles
>
> no it doesn't
Shure?

Before sending bug report I did the following:

- run gnome-system-log
  it shows the known list of nonexistant logfiles

- run gconf-editor and deleted '/apps/gnome-system-log/logfiles' value
  btw. it was empty but it says it is of the type bolean, strange I would say
  nevertheless I deleted the value

- restarted gconf-editor and it attempts to open the bogus input files again
  ('/apps/gnome-system-log/logfiles' value was empty)

- did a reboot

- '/apps/gnome-system-log/logfiles' shows the list as in
  "--8<--from gnome-system-log --8<--", see below.

- deleted nonexistant files in '/apps/gnome-system-log/logfiles'

- restarting gnome-system-log and voilla, no complains about nonexistant files
  anymore

---8<--- from gnome-system-log ---8<---
Could not open the following files:
/var/log/XFree86.0.log: Fehler beim Untersuchen der Datei
/var/log/XFree86.0.log mit fstat(): No such file or directory
/var/log/cron: Fehler beim Untersuchen der Datei /var/log/cron mit fstat(): No
such file or directory
/var/log/maillog: Fehler beim Untersuchen der Datei /var/log/maillog mit
fstat(): No such file or directory
/var/log/secure: Fehler beim Untersuchen der Datei /var/log/secure mit
fstat(): No such file or directory
/var/log/sys.log: Fehler beim Untersuchen der Datei /var/log/sys.log mit
fstat(): No such file or directory
---8<--- ---8<--- ---8<---

So I would say at least for the first run gnome-system-log uses the hardcoded
logfile-list nevertheless if thes exist or not.

reegards,
thomas