Re: [Gnumed-devel] permission problem for .gnumed directory

[Karsten Hilbert]

> Today we encountered a strange problem. When the directory
> /home/user/.gnumed  belongs to root
Why the heck would that be ?

> GNUmed will not start and complain about missing modules
> for  version 0.2.8.10
> 
> Cannot open any log file.
> 
> Critical ERROR: Cannot load GNUmed Python modules ! - Program halted
Yep, because the gmLog.py fails to import.


> For version 0.3.2 it complains like this and will not start:
> 
> gnumed
> Traceback (most recent call last):
>   File "/usr/lib/python2.5/site-packages/Gnumed/wxpython/gnumed.py", line
> 378, 
> in <module>
>     setup_logging()
>   File "/usr/lib/python2.5/site-packages/Gnumed/wxpython/gnumed.py", line
> 156, 
> in setup_logging
>     from Gnumed.pycommon import gmLog2 as _gmLog2
>   File "/usr/lib/python2.5/site-packages/Gnumed/pycommon/gmLog2.py", line
> 265, 
> in <module>
>     __setup_logging()
>   File "/usr/lib/python2.5/site-packages/Gnumed/pycommon/gmLog2.py", line
> 214, 
> in __setup_logging
>     _logfile = codecs.open(filename = _logfile_name, mode = 'wb', encoding
> = 'utf8', errors = 'replace')
>   File "/usr/lib/python2.5/codecs.py", line 817, in open
>     file = __builtin__.open(filename, mode, buffering)
> IOError: [Errno 13] Permission denied: '/home/basti/.gnumed/gnumed-6638.log'

Quite clear and logical (to a programmer) ;-)

> We should try to write to temp then instead
Nope, the log can potentially contain sensitive patient data. In fact, we 
should assure that both
the log file and /home/basti/.gnumed/ are 0600 (the dir needs -x-, too, I know).

> or run without a log file.
Nope, we cant diagnose problems without it.

But we should make GNUmed complain in a better way :-)

Please file as wishlist bug.

Karsten
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: 
http://www.gmx.net/de/go/multimessenger