[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] FP2000 user webs and SSL
- Subject: Re: [cobalt-users] FP2000 user webs and SSL
- From: Will DeHaan <will@xxxxxxxxxx>
- Date: Thu Dec 2 19:13:25 1999
- Organization: Cobalt Networks
Not to worry, everything can be fixed with a little attention...
All directories from /home/sites/www.customer.com/ must be owned by the
appropriate group called siteX (the directory name that
/home/sites/www.customer.com is a symbolic link to.) You can enable
sticky bits for a site by running "chmod g+s directoryname" where
directoryname would be the name for the directory. The sticky bit
forces files that are created in that directory to assume the group
ownership regardless of whether the user creating those files is a
member of that group or not. Group quota is equivalent to site quota.
So if group ownership is lost, site quotas don't mean much.
The best way to make sure your directory ownership and permissions are
in their intended state is to create a new site, add a user or two and
compare the new site with the older, hacked and re-hacked site.
My apologies to anyone who doesn't understand my babble but this is not
of importance if you haven't been playing with frontpage as root on a
RaQ 2 or 3i.
-- Will
Clayton McGow wrote:
>
> Will,
>
> Yow! Although my sites appear to be working fine, sounds like I made a
> bad mistake... what is the correct way to set the owner, or should they
> be left as httpd? If so, won't that mess up fpweb publishing for users?
>
> Will DeHaan wrote:
> >
> > Don't call fpsrvadm.exe from the command line on RaQ 2 or RaQ 3i servers
> > as it will badly mess up directory permissions, throwing a wrench into
> > site and user quotas.
> >
> >
> > -- Will
> >
> > Clayton McGow wrote:
> > >
> > > Jim,
> > >
> > > if you go to /usr/local/frontpage/currentversion/bin and run
> > > fpsrvadm.exe, you'll see an option to chown the fpweb to whoever is
> > > supposed to own it.
> > >
> > > Jim Euliano wrote:
> > > >
> > > > >and enables it, suEXEC changes the uid and gid on scripts to httpd
> > > > >instead uid of the user (see below). The reason the main web still
> > > > >works is because it is supposed to be owned by uid httpd. To correct
> > > >
> > > > I've found that almost all of my web pages (cgi files, html files, gif and
> > > > jpg files, etc etc) are now owned by httpd. The group id hasn't changed
> > > > from whatever site they belong to... but the uid for almost every web file
> > > > on my system is httpd. I do not have the SSL pack installed.
> > > >
> > > > Did I mess something up somewhere along the line... is this normal... or am
> > > > I just wacko. It isn't a problem for me yet, so I don't really care... I
> > > > was just wondering if it was related.
> > > >
> > > > Jim
> >
> > _______________________________________________
> > cobalt-users mailing list
> > cobalt-users@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-users
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users