I am unable to examine Apache httpd error log from YaST2 because the lines are too long; the browser just truncates them and thus it does not show any description. The only option is to save it. However, when I chose that option, YaST2 encourages me to save it in [/tmp](file://tmp/), and as soon as I do that, the log becomes accessible to every user!
SNAFU,
Chris
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So… you have your umask set to 0022, then you use ‘root’ to open a
potentially sensitive file, then you choose to save it in a world-readable
area, and that’s a bug? If you say so… submit a bug report at
http://bugzilla.novell.com and post back the bug number.
On a SLES 10 system I have (old, I know) I did the same steps. In my case
there is line wrapping in the error_log display so saving it out wasn’t
necessary, though when I did something ill-advised like saving sensitive
data with read permissions to a world-readable area (rather than in /root
or something) it did have 0644 permissions because I have not changed the
default umask.
Good luck.
On 11/14/2010 12:36 PM, yecril71pl wrote:
>
> I am unable to examine ‘Apache httpd’ (http://httpd.apache.org/) error
> log from YaST2 because the lines are too long; the browser just
> truncates them and thus it does not show any description. The only
> option is to save it. However, when I chose that option, YaST2
> encourages me to save it in ‘/tmp’ (file://tmp/), and as soon as I do
> that, the log becomes accessible to every user!
> SNAFU,
> Chris
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM4MOjAAoJEF+XTK08PnB5HI8P/33uG5nk39lPDKFqEGHRwV6E
y4PBzLzMhXU93NUSDcQhV72lShfpHdeMbYtSpkD8mW1yL6UXLr4E3nq3rHnTV2Mu
csBHJqQswHAPVsE99625yOjp6STlBbSBiWu9y9DjhMn3vgy+mWBjN3Z8lzNdgg39
S8ONyWKH08pn/c07WTUWAbFn3KyFioiOdGrEo4kHDgrDCQ86kfUmbvvXMKq53d+P
GJ3QUB8ay8pLfrP4yWQ1EqFh+5uVhL5HVxwRubdDV9hvZQVJEZqUmrzjKmAQ0cWd
Ow8E9GW6wpqIMKWCi9TIDtFVPbvwnaFrvKAiypFTRcMs/43EDlt52tb0YmPFCRxu
LidY5h98XQHdaUc7z1285m6Ew9amYHgDKj26fHA0L2sv6lEa1hxmQIUoMtemkfyV
OXdl0kVjYE07AYyPzYd8wJ54QFy+ehrqJKLWnrz7X/bh4FItuGKWbWCmMDuj0txG
lQIC5cY0Xc5yahULU9O8Hlq5R6sfdIVj3vFt9CEzNsXpeZ809Jy+vX5r8TkIckPy
mHipmlMpxACJ3e9M4tubVo9lI+9heaLGpnaTdPuppVynfhy3uSf3vKdKqYTyeBVf
Ds+1R2LrcFwczdXYb0dY5dmhRbp4krXHyrh0224YKiQYjPIgvKMeFeM7WM/RNTJl
7Q9dlKx0DdwvBkH96oci
=lflp
-----END PGP SIGNATURE-----
It’s true that YaST offers to save the log to /tmp (the code is at /usr/share/YaST2/modules/LogView.ycp:399).
But when I look at /var/log/apache2/, I see that the log files are world-readable by default, so YaST does not make it any worse.
Argh, scratch that. /var/log/apache2 itself is not readable by world.
Yast may be good for many things, but to check my apache log files I use:
# less /var/log/apache2/error_log
# less /var/log/apache2/access_log
You need root privileges to read the files.