Chuck, thanks for the valuable advice! I created /etc/security/msec/perm.local with just one line:
/home/PgDB postgres.postgres 700 and it seems to have done what I want (after running 'msec' of course). Thanks a bunch! Daniel, thanks for the links, I'll definitely check the info. Just wanted to get this working first :) Aleksey On Tue, 13 Aug 2002, Chuck Shirley wrote: > On Tuesday 13 August 2002 15:15, Aleksey Y Naumov wrote: > >Dear experts, > > > >I have I question/problem with msec on my 8.2 system: it keeps changing > >permissions on directory /home/PgDB. /var/log/auth.log has: > >... > >Aug 13 > >15:01:00 ples msec: changed mode of /home/PgDB from 700 to 755 > >... > > > >Trouble is, this is my data directory for PostgreSQL database, so it has > >to have permission 700, i.e.: > >drwx------ 6 postgres postgres 4096 Aug 13 14:56 PgDB/ > > > > It took me quite a while to figure this out myself. I haven't tried with > a directory, but it works with individual files. Put the file, it's owner > and group, and the permissions you want it to have in > /etc/security/msec/perm.local, like so: > > # /etc/security/msec/perm.local > # Local file permission settings to override msec. > # [file] [uid.gid] [perms] > # > /usr/bin/artswrapper root.root 4755 > > (This example keeps msec from turning off suid on the artswrapper > so that my artsd can run with NRT scheduling priority) > > Probably, the file is empty, at least it was on my system, so once > I figured out the format, I created the header to keep me from having > to go through all the headache again. Sadly, msec is not well documentd > unless you can read perl really well! :^) > > -Chuck > > -- > +-% He's a real UNIX Man $-+-------------------------------------+ > \ Sitting in his UNIX LAN \ Charles A. Shirley \ > \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ > +------# For nobody @------+-------------------------------------+ > > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
