[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] /~username to /username for virtual site
- Subject: Re: [cobalt-users] /~username to /username for virtual site
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Mon Jan 20 23:39:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
ME> Date: Sun, 19 Jan 2003 19:17:57 +1100
ME> From: Mitchell Essex
ME> I have had a look through the archives and there seems to be
ME> some mention of doing this automatically but I am unsure how
ME> it works there was something about using the AliasMatch or
ME> using a RewriteRule for the site.
Rewrite rule.
ME> This is how I can manually do it as root
[ editted slightly to accomodate line wrap, but equivalent ]
ME> ln -s /home/sites/sitename/users/username/web \
ME> /home/sites/sitename/web/username
ME> chown username /home/sites/sitename/web/username
ME>
ME> This creates a link from the users home directory web to the
ME> web directory of the site, but how would virtual site
ME> administrators do this for themselves. They would be able to
ME> link to the directory but not change the ownership of the
ME> link.
Why are you concerned about symlink ownership? Or do you mean
the target of the link? This way looks a bit messy, if I
understand your goal correctly.
I suppose one could write a *shudder* setuid root chown program
that changed ownership after a few safeguards -- much like a CGI
wrapper.
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.