
Bugtraq mailing list archives
Re: Veritas Volume Manager 3.0.x hole
From: seeger () CISE UFL EDU (Charles Seeger)
Date: Tue, 20 Jun 2000 16:18:12 -0400
+------ Doug Hughes wrote (Sun, 18-Jun-00, 19:09 -0500): | On Fri, 16 Jun 2000, Dixie Flatline wrote: | > | > Workaround & Comments | > --------------------- | > | > The trivial workaround: add "umask 022" to /etc/rc2.d/S96vmsa-server | > before the line that starts the Storage Administrator Server. | | Don't edit the file. It'd just be changed on the next upgrade, or possibly | even the next patch. It's much better to add a new file in rcS.d, rc2.d, | and rc3.d called S00umask.sh (one in each dir - or link it) | in the files put: | umask 022 | It's good innoculation against spurious /tmp files, and it has been | recommended practice for many years. Great advice, but let me add that the ".sh" extension to the file name is crucial for this to operate properly. Otherwise the script will be executed by a seperate child sh instance rather than being sourced by the calling script. Best Regards, Chuck -- Charles Seeger <seeger () cise ufl edu>
Current thread:
- Re: Veritas Volume Manager 3.0.x hole Charles Seeger (Jun 20)