I think I am understanding that all the e-smiths that I have setup so far have had a
configuration error then.
Hmm... I wonder if that reflects on the operator?
( in 4.0 and 4.0.1)
if I leave that setting at e-smith then I have to address my machine
www.e-smith.e-smith.mydomain.com and if I change it to anything else I have to address
my
machine www.e-smith.mydomain.com (note the name I put in there is not in the name at
all)
replace www part of name with any of the others that you mentioned also. (mail, proxy
etc...)
But that must be a configuration problem on an older version 4.0 and 4.0.1 so we can
leave it for now and I will attempt to see where I went wrong next time I get out
there.
Gordon Rowell wrote:
> On Wed, Dec 20, 2000 at 10:30:18PM -0600, Tim Litwiller <[EMAIL PROTECTED]>
>wrote:
> > Sorry about not checking the reply address Gordon here it is for
> > the list:
>
> No worries - I like to see these things debated in public.
>
> > I guess you and I understand that just a little different,
>
> Probably :-) We've debated this a lot of times internally. We're still
> open to being swayed. The options are configurable - the question
> boils down to the correct default behaviour.
>
> 4.0[.1] used a static tag 'e-smith', which was annoying to many
> people. One option was to follow the $ServerName, but that would mean
> that multiple servers would have different domain names, which isn't
> logical. Not having a sub-domain causes problems for people who have
> externally hosted www sites.
>
> The "Hostnames and Addresses" module is designed to address these
> problems, allowing you to set local and remote names. The user
> interface still needs a bit of work, but it does cater for the various cases:
>
> - Local network hostname
> - Alias for local interface of e-smith server
> - External network hostname (e.g. off-site www.{domain}
> - Alias for external interface of e-smith server
> - Alias for external host behind port-forwarding firewall
>
> > I still want the e-smith server to use www.mychoice.mydomain.com
> > just not www.e-smith.mydomain.com if you ask for a name then why not
> > use it?
>
> Unfortunately, there is no right solution which fits in all cases. We
> don't want people to have to change their domain name just because
> they've decided at a later stage to have an externally hosted
> WWW/FTP/etc. site.
>
> > It seems it is not a bug just very confusing since you suggect
> > leaving it set to e-smith and if you change it during configuration
> > it doesn't use the name anyways.
>
> It does change - names just have $conf{'LocalDomainPrefix'}
> inserted. It is now configurable to any value (even nothing at all).
>
> By default, we prime the hosts database with:
> mail
> www
> ftp
> proxy
> e-smith-manager
>
> which point to the internal side of the e-smith server. These names
> must be defined - but they can be repointed to any hosts you like.
>
> So, by default, http://www goes to the e-smith server. You can now
> override that with an explicit setting for www -> some random external
> IP address. FYI - the e-smith-manager name is there so that people can use:
>
> http://e-smith-manager
>
> as the default URL, which works whether they have on-site or off-site
> www.
>
> Hmm, I think I've just argued that LocalDomainPrefix can now be empty
> by default and $DomainName is used verbatim. We would need some strong
> wording to warn people about hiding real Internet names...
>
> Gordon
> --
> Gordon Rowell [EMAIL PROTECTED]
> http://www.e-smith.org (development) http://www.e-smith.com (corporate)
> Phone: +1 (613) 564 8000 ext. 4378 Fax: +1 (613) 564 7739
> e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
