Very Computer

Does Netscape do that, OpenMarket do that, Or otehrs?

Thanks,

zhao

|>Is there any httpd package that could do not only multi web-home
|>setup, but also
|>   email for multi-doamin-names with their own domain-name;
|>   store log files for each domain-name in their own location;
|>   setup cgi-bin for each domain-name to have their own directory;
|>   support autherization and configuration for their own home
The last three are supported by netscape and apache, and probably anybody who
does virtual hosts.  I'm not really sure what you're asking with the first
question, but I THINK the answer is you do it with mx records in your DNS
server.
--
Jim Feldman, Digital Equipment Corp

My opinions are my own and in no way reflect Digital's POV (unless they're
charging somebody for me to give them).

It doesn't matter who you are, or what you've done, or think you can do.
There's a confrontation with destiny awaiting you.  Somewhere, there is
a chile you cannot eat.
                -- Daniel Pinkwater, "A Hot Time in Nairobi"

1. Multi-homed e-mail

   You need to use a mailertable in Sendmail. There's a sendmail user group
   you'll be able to get some help from. This will involve some knowledge
of sendmail re-writing rules on which there are books. It's not the most
user-friendly of config files but you'll soon get the hang of it.

2. Log files.

   Using, eg., Apache's virtual server hack, you can either store them in
a separate place or, and probably more useful, prepend a sentinel at the
beginning of the line and then grep out the results to do your logs. eg.,
on my server, all logs for personality.co.uk read something like:

You can then grep the appropriate entries out to do your stats. This has
an added advantage of keeping it all in one place and being able to do a
tail -f on the file to monitor *all* incoming requests.

3. cgi-bin: You can do /cgi-bin/username instead. This way you can more
easily manage your clients' data. You may be able to do a symbolic link
from their home-dir and allow them to access their cgi data that way.
Otherwise, allow them to run CGIs from their own site instead.

4. Authorisation and configuration from the home can sensibly and securely
be achieved using CGIs or configuration files. You'll have to decide what
you want the user to be able to configure and sort it out from there.
Sorry, can't be more helpful because I'm not sure what you want your
customers to be able to change.

Andrew.

--
Andrew Crane, Surrey, England - Internet and prepress consultant
Programming services in 'C', unix, perl, PostScript, applescript

Quote:>     store log files for each domain-name in their own location;
>     setup cgi-bin for each domain-name to have their own directory;
>     support autherization and configuration for their own home

                Elf !!!
--
Elf Sternberg                 Geeks are neither skilled nor curiousities,

Public key available                http://www.halcyon.com/elf/index.html