BUG: ADSM Solaris, world-writable dsmerror.log

BUG: ADSM Solaris, world-writable dsmerror.log

Post by Niklas Edmundsso » Sat, 21 Aug 1999 04:00:00

In recent versions of the ADSM-client for Solaris (both the 2.5 and
2.6-version) we have noticed that the log-file dsmerror.log is always
created world-writable. Setting the umask of dsmc or chmod:ing an
existing dsmerror.log doesn't help, as soon as dsmc gets near it gets
world writable again...

The most recent Solaris 2.6 client has IP21630 installed.

This is a very obvious bug (as I can't imagine it is a feature ;) and it
can't be especially hard to fix. IMHO it should never have appeared ;)

/Nikke - not fond of world-writable logs.

 That was a pointing device? My cat thought it was dinner.


1. apache world-writable logs created by rotatelogs after a boot

I'm running apache 1.3.9 and have the ErrorLog and CutomLog directives
configured to pipe to "rotatelogs". The configuration of these
directives includes an "exec" after the "|" as per bug #PR3713. The OS
is Solaris 2.6.

This all seems to work fine except when the system is down at rotation
time. The new access and error logs created after the system is booted
are world writable. Also the ownership of these files is root:root as
opposed to the usual root:other.

Are these world writable file typical for rotatelogs running under
apache 1.3.9 on Solaris 2.6? If so, is there some way to prevent the
creation of post-boot world-writable log files?

Sigrid Illes

2. Two Senior Unix Engineering positions available in Minneapolis, MN

3. How to make a world-writable file not world-deletable...?

4. XF86Setup Startup File

5. World-writable files?

6. Solaris 8, fpversion missing "-"

7. Dumping world-writable bit on /usr/spool/mail

8. browser problems

9. in.ftpd creating world-writable files (partial fix), & a question

10. World-writable directories..

11. World-writable files

12. World writable, why?

13. Q: mounting DOS partitions world writable