Wiki listed under other virtual hosts

I have a wiki where under "Settings > Advanced" it is set to be restricted to a specific hostname. Using http://www.myhost.com/groups/mywiki I can access the wiki fine, and I see it listed when I go to http://www.myhost.com/groups/. If I try to access the wiki using a different hostname (e.g. http://www.otherhost.com/groups/mywiki ), I get a 404 error (so far so good). However, if, using this other hostname, I ask for a list of available wikis (i.e. http://www.otherhost.com/groups/) the wiki is listed there, even if I get a 404 when I click on it. Shouldn't the wiki be invisible? How do I make it so that the wikis under one virtual host are completely isolated from other virtual hosts?
I have tried deleting and recreating the wiki; turning the Settings > Advanced on and off; etc etc. Same behavior each time.

Ditto.
I noticed it when logged in as a user with permissions to a specific wiki on the server, and went to 'My Page', that updates from all the other wikis on the server are listed, in addition to the updates for the wiki I belong to. I can't get to them by clicking on the links, but they show up in the list. Makes it pretty hard to focus on your wiki, when you see updates from multiple other wikis listed.
It would seem like there must be a fix in the code for both the 'My Page' and the generic top-level '/groups', but I don't know the code structure well enough yet to figure out how/where to fix it.
Anyone else find a solution for this? I don't think I can roll out multiple domains/wikis on one server, if this behavior is present.

Similar Messages

Corrupted wiki list with multiple virtual host

Hello,
I have several virtual hosts and I want each of them to only list of wikis which are associated with them using the Wiki Admin Settings -> Advanced : Specific Host Names.
This does not seem to work. As soon as a wiki is associated to a specific virtual host it disappears from the list of wiki (http://hostname/groups/) (on all virtual hosts actually). The wiki itself can still be accessed by its explicit address: http:/hostname/groups/wikiname
If I manually edit the sql3 file directoryIndex.db in /Library/Application Support/Apple/WikiServer
and replace the specific host name by "*", the wiki reappears in the wiki list but on ALL virtual host. Still it remains accessible only in the one designated in the wiki Settings.
Most frustrating. Any workaround ? Seems like a bug but the wiki implementation being so convoluted I am not completely sure.
Any help ?
Thanks
Paul

Hi,
Seems to work on my test ASA
Attached it to my current LAN interface.
ASA(config)# packet-tracer input LAN tcp 10.2.11.1 12345 64.156.192.154 80
Phase: 1
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in 0.0.0.0 0.0.0.0 WAN
Phase: 2
Type: ACCESS-LIST
Subtype: log
Result: ALLOW
Config:
access-group outbound_access in interface LAN
access-list outbound_access extended permit object-group obj_Meraki_outbound object-group obj_Meraki_lan object-group obj_Meraki_pub
object-group service obj_Meraki_outbound
service-object tcp destination eq https
service-object tcp destination eq www
service-object tcp destination eq 7734
service-object tcp destination eq 7752
service-object udp destination eq 7351
object-group network obj_Meraki_lan
network-object 10.2.11.0 255.255.255.240
network-object 10.5.11.0 255.255.255.240
object-group network obj_Meraki_pub
description: This group lists all hosts associated with Meraki.
network-object host 64.156.192.154
network-object host 64.62.142.12
network-object host 64.62.142.2
network-object host 74.50.51.16
network-object host 74.50.56.218
Additional Information:
access-list outbound_access line 1 extended permit tcp 10.2.11.0 255.255.255.240 host 64.156.192.154 eq www (hitcnt=1) 0x4d812691
Also have used such configuration in some special cases where the customer has insisted on allow specific TCP/UDP ports between multiple networks. And nothing is stopping from adding ICMP into the "object-group service" also.
- Jouni

How do you delete a phone number from an iphone that is listed under other and not in the contacts list?

When I text a contact in my iphone 4s the name will show up like it should but it has the persons current phone number and another or their old number listed under other. Its not in my contacts on my laptop anywhere so how do I delete that old number, I have looked in my phone contacts its not there but its like the email addressess show up to if you start typing an email address will show up even if its not one in your contacts.

Did you manage to resolve this issue?
I called Apple Care, tried various things that did not work, then completely reset my iPhone 5 and restored from a recent backup. That worked for a day or so, then the definct "other" number was again offered when I started typing the name of a contact whom I wanted to text.

Hello, alot of my space taken up on my ipod nano is listed under (other) I don't know what this is but it sure takes up most of the space on my ipod. Does anyone know what (Other) refers to and how to remove it.?Thx

Hello, alot of my space taken up on my ipod nano is listed under (other) I don't know what this is but it sure takes up most of the space on my ipod. Does anyone know what (Other) refers to and how to remove it.?Thx

Hello Norman,
Welcome to the Apple Support Communities. To find out what the Other section is on your iPod Nano, the following will explain what the Other section is all about.
Understanding capacity on iPhone, iPad, and iPod
http://support.apple.com/kb/HT1867
Once that is complete, then check the appropriate sections to see what is there. If you cannot isolate the issue then you may need to restore the iPod Nano. The following will assist with the restore process.
Restoring iPod to factory settings
http://support.apple.com/kb/HT1339
Regards,
-Norm G.

Separate Wiki Data Stores for Virtual Hosts?

Is it possible to set different data stores to be used for the wikis associated with different sites (i.e. virtual hosts) on a Mac OS X Server (Snow Leopard)?
By default they are in "/Library/Collaboration/" and that is applied to ALL hosted sites.
My client would like a little more differentiation than that offered by user and/or group login.
Thanks in advance.
+*Geoff Heys*+

Ditto.
I noticed it when logged in as a user with permissions to a specific wiki on the server, and went to 'My Page', that updates from all the other wikis on the server are listed, in addition to the updates for the wiki I belong to. I can't get to them by clicking on the links, but they show up in the list. Makes it pretty hard to focus on your wiki, when you see updates from multiple other wikis listed.
It would seem like there must be a fix in the code for both the 'My Page' and the generic top-level '/groups', but I don't know the code structure well enough yet to figure out how/where to fix it.
Anyone else find a solution for this? I don't think I can roll out multiple domains/wikis on one server, if this behavior is present.

Storage capacity is stated as being full, but all audio, video, apps, docs, etc. only add up to 7.6 GB out of 12 GB. iTunes shows that I am all of a sudden using 5.6 GB listed under "OTHER". What happened?

Why is storage capacity shown as full when it is not? Phone shows storage of only 7.6 GB out of 13 GB, but says I have no more storage. iTunes indicates I am using 5.6 GB under the category "OTHER". This is a sudden change. What happened?

What is "Other" and What Can I Do About It?- Apple Support Communities

Virtual Hosts in Apache HTTP Server

How to configure virtual hosts in Apache HTTP Server httpd.conf file.
If I want to access my server with some other name(alias), how can I do this ?
Suggestions in this matter would be highly helpful.
Thanks
Vidhyut Arora

Following is a note explaining how to setup
Virtual hosts.
Hope this helps
Ranga
Note:70647.1
Subject: Apache Server Virtual Hosting
Last Revision Date: 07-JUN-2001
PURPOSE
This document discusses considerations for setting up virtual hosts on an
Apache machine, to include how to get the hostname working and how to
configure Apache.
SCOPE & APPLICATION
The information in this document is intended for those who manage multiple sites
using an Apache machine.
REFERENCES
First published in Apache Week issue 31 (6th September 1996)
Last update 20th September 1998
Using Virtual Hosts
Virtual Hosts let you run multiple independent Web sites on a single host with
a single Apache setup.
One of the most important facilities in Apache is its ability to run virtual
hosts. This is now the essential way to run multiple Web services - each with
different host names and URLs - that appear to be completely separate sites.
This is widely used by ISPs, hosting sites and content providers who need to
manage multiple sites but do not want to buy a new machine for each one.
Picking an IP address
There are two types of virtual hosts: IP-based and non-IP-based. The former is
where each virtual host has its own IP address. You must have a new IP address
for each virtual host you want to set up, either from your existing allocation
or by obtaining more from your service provider. When you have extra IP
addresses, you tell your machine to handle them. On some operating systems, you
can give a single ethernet interface multiple addresses (typically with an
fconfig alias command). On other systems, you must have a different
physical interface for each IP address (typically by buying extra ethernet
cards).
IP addresses are a resource that costs money and are increasingly difficult to
get, so modern browsers can now also use 'non-IP' virtual hosts. This
lets you use the same IP address for multiple host names. When the server
receives an incoming Web connection, it does not know the hostname that was used
in the URL. However, the new HTTP/1.1 specification adds a facility where the
browser must tell the server the hostname it is using, on the Host: header. If
an older browser connects to a non-IP virtual host, it does not send the Host:
header, so the server must respond with a list of possible virtual
hosts. Apache provides some help for configuring a site for both old and new
browsers.
Picking a Hostname and Updating the DNS
Having selected an IP address, the next stage is to update the DNS so that
browsers can convert the hostname into the right address. The DNS is the system
that every machine connected to the internet uses to find the IP address of host
names. If your hostname is not in the DNS, no one can connect to
your server (except by the unfriendly IP address).
If the virtual hostname you are going to use is under your existing domain,
you can just add the record into your own DNS server. If the virtual hostname
is in someone else's domain, you must get them to add it to their DNS
server files. In some cases, you want to use a domain not yet used on the
internet, in which case you must apply for the domain name from the
InterNIC and set up the primary and secondary DNS servers for it, before adding
the entry for your virtual host.
In any of these cases, the entry you need to add to the DNS is an address record
(an A record) pointing to the appropriate IP address. For example, say you want
the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
must add the following line to the DNS zone file for my-dom.com:
www A 10.1.2.3
Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
to your Web server. However, it will return the same information as if the
machine's original hostname had been used. So, the final stage is to tell Apache
how to respond differently to the different addresses.
How Apache Handles Virtual Hosts
Configuring Apache for virtual hosts is a two-stage process. First, it needs
to be told which IP addresses (and ports) to listen to for incoming Web
connections. By default, Apache listens to port 80 on all IP addresses of the
local machine, and this is often sufficient. If you have a more complex
requirement, such as listening on various port numbers, or only to specific IP
addresses, then the BindAddress or Listen directives can be used.
Second, having accepted an incoming Web connection, the server must be
configured to handle the request differently, depending on what virtual host it
was addressed to. This usually involves configuring Apache to use a different
DocumentRoot.
Telling Apache Which Addresses to Listen To
If you are happy for Apache to listen to all local IP addresses on the port
specified by the Port directive, you can skip this section. However, there are
some cases where you want to use the directives explained here:
- If you have many IP addresses on the machine but only want to run a Web
server on some of them
- If one or more of your virtual hosts is on a different port
- If you want to run multiple copies of the Apache server serving different virtual
hosts
There are two ways of telling Apache what addresses and ports to listen to:
- Use the BindAddress directive to specify a single address or port
- Use the Listen directive to any number of specific addresses or ports
For example, if you run your main server on IP address 10.1.2.3 port 80, and a
virtual host on IP 10.1.2.4 port 8000, you would use:
Listen 10.1.2.3:80
Listen 10.1.2.4:8000
Listen and BindAddress are documented on the Apache site.
Configuring the Virtual Hosts
Having gotten Apache to listen to the appropriate IP addresses and ports, the
final stage is to configure the server to behave differently for requests on
each of the different addresses. This is done using <VirtualHost> sections in
the configuration files, normally in httpd.conf.
A typical (but minimal) virtual host configuration looks like this:
<VirtualHost 10.1.2.3>
DocumentRoot /www/vhost1
ServerName www.my-dom.com
</VirtualHost>
This should be placed in the httpd.conf file. You replace the text
10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
port as well, follow the IP address with a colon and the port number
(example: 10.1.2.4:8000). If omitted, the port defaults to 80.
If no <VirtualHost> sections are given in the configuration files, Apache
treats requests from the different addresses and ports identically. In terms of
setting up virtual hosts, we call the default behavior the main server
configuration. Unless overridden by <VirtualHost> sections, the main server
behaviour is inherited by all the virtual hosts. When configuring virtual
hosts, you must decide what changes to make in each of the virtual
host configurations.
Any directives inside a <VirtualHost> section apply to just that virtual host.
The directives either override the configuration give in the main server, or
supplement it, depending on the directive. For example, the DocumentRoot
directive in a <VirtualHost> section overrides the main server's DocumentRoot,
while AddType supplements the main server's mime types.
Now, when a request arrives, Apache uses the IP address and port it arrived on
to find a matching virtual host configuration. If no virtual host matches the
address and port, it is handled by the main server configuration. If it does
match a virtual host address, Apache uses the configuration of that virtual
server to handle the request.
For the example above, the server configuration used is the same as the
main server, except that the DocumentRoot is /www/vhost1, and the
ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
that deal with handling requests and resources are valid inside <VirtualHost>
sections. However, some directives are not valid inside <VirtualHost> sections,
including BindAddress, StartSevers, Listen, Group and User.
You can have as many <VirtualHost> sections as you want. You can
leave one or more of your virtual hosts being handled by the main server, or
have a <VirtualHost> for every available address and port, and leave the main
server with no requests to handle.
VirtualHost sections for non-IP Virtual Hosts
Non-IP virtual hosts are configured in a very similar way. The IP address that
the requests arrive on is given in the <VirtualHost> directive, and the
host name is put in the ServerName directive. The difference is that there
(usually) is more than one <VirtualHost> section handling the same IP address.
For Apache to know whether a request arriving on a particular IP
address is supposed to be a name-based requests, the NameVirtualHost directive
addresses for name-based requests. A virtual host can handle more than one
non-IP hostname by using the ServerAlias directive, in addition to the
ServerName.
null

Publish Abap Web Service in ICF virtual host

Hello
We have configured our abap aplication server with two virtual host in SICF
one the default_host that listen in http 8080 port and other virtual host that
listen in http 8090 port.
We need define some ABAP web services that listen in default_host:8080 and other virtual host in virtualhost2:8090.
We define de web service with SE80 wizard and then create the configuration end point
with SOAMANAGER.
Our problem is that soamanager ever create the entrie of endpoint in sicf transaction, under default_host:8080 service tree not under virtualhost2 service tree. and so we can not call
the web service like http://virtualhost2:8090/sap/bc.... because don't exist, only exist
http://defaul_host:8080/sap/bc....
we try to copy the entry of the tree under virtualhost2 in the proper place of the tree,
but when call the webservice with soaui the system report the error:
No Web service configuration for this access path: ""
i can see that there are entries in the table SRT_CFG_SRV_ASGN that are related with this
problem, because assign the url of the endpoint of the ws to virtual host, but i don't
know how the system generate this entries.
someone know how call ABAP web service with icf virtual host?
thanks
regards
diego

Hi Trevor
For test purpose i can do it works.
The key point is create the proper entry in the table SRT_CFG_SRV_ASGN that refer to the correct VIRTUAL_HOST.
When you genreate the endpoint of the service with soamanager, the system generate an entrty in this table with the fiel VIRTUAL_HOST = 0, you can copy this entry and change only two fields.
VIRTUAL_HOST = <the number of your virtual host>
HASH --> you can calculate this field with the FM CALCULATE_HASH_FOR_CHAR, in the parameter DATA contatenate the content of the fiels VIRTUAL_HOST and URL (be careful with the upercase), this function module return you the hash.
(First you have to replicate the icf tree that soamanager create under your virtual host tree)
With this configuration i can call to my WS over the virtaual host, using soaui.
I hope this can be useful for you.
Regards
diego

Virtual host (vod) map location of files

I have my virtual host working in Adobe Interactive Server 4.0 however:
inside of my virtual host:
myvid1.domain.com
/opt/adobe/fms/conf/_defaultRoot_/myvid1.domain.com/
I have these directories & files
-rw-r----- 1 fms fms 55318 Aug 2 15:12 Application.xml
drwxr-xr-x 2 fms fms 4096 Aug 2 19:17 live
-rw-r----- 1 fms fms 55318 Aug 2 12:49 Org_Application.xml.bak
-rw-r----- 1 fms fms 15811 Aug 2 10:48 Org_Vhost.xml.bak
-rw-r----- 1 fms fms 15960 Aug 2 19:25 Vhost.xml
drwxr-xr-x 3 fms fms 4096 Aug 2 19:16 vod
I have the vod and live directories
however my virtual host is not pulling the data from the (vod directory)
is there another file that needs to be changed to read from this directory?
Any help would be great.
thanks

I was told by one of the Adobe people when we purchased the Interactive Server to copy the 'live' and 'vod' under the virtual host directory.
Thank you for letting me know this is not needed here, I will get rid of them.
The server pulls data from the following:
/opt/adobe/fms/applications
the 'live' and 'vod' directories the data is being pulled from here.
The connection is successful, however I want each 'virtual host' to pull from its own data directory so the user data will be isolated and not viewable.
How can I successfully change the 'vod' and 'live' directory on each virtual host this is my objective.
So then I can change ownership of the 'vod' directory and create a username/password for the site owner to ftp data to the server.
Lastly, is the main.asc (that is where the user name and password goes to prevent anyone from streaming live to the server?
/opt/adobe/fms/applications/livepkgr
[sysadmin@fmsvideo01 livepkgr]# ls -l
total 24
-rwxrwxrwx 1 fms fms 733 Jul 29 09:57 Application.xml
drwxrwxrwx 3 fms fms 4096 Jul 29 09:57 events
-rwxrwxrwx 1 fms fms 3941 Jul 29 09:57 main.asc <- - - - - (is this the security file)???
What I want to do is incorporate this code to prevent unauthorized connections to publish live to the server.

Virtual Host Problem !!!!!

I have few virtual host on a Iplanet Web server 6.0 SP2 , One of the application / virtual host has stopped running, giving error "page cannot be displayed", HTTP/1.1" 500 335.
I checked the logs as well but the error logs is also not getting any error message.
I am also now not able to run a simple HTML file on this virtual host.
I have other virtual hosts on the same server instance and they are running absolutely fine.
Has anyone faced this kind of problem?
URGENT !!!!!!!!

bzoler wrote:
I have configured a virtual hos t on my weblogic 7 server
but it doesn't work
are there some special thing to do
to make it work?Could you please be more specific about what you mean by "doesn't work"?
Try posting WLS questions to weblogic.developer.interest.servlet or
weblogic.developer.interest.webserver newsgroups.
Subbu

First listed virtual host is masking others

I am running a couple of virtual hosts started through the standard Server Admin GUI. All vhosts are name-based. I have three:
default (no domain name, port 80)
site1 (site1.myschool.edu, port 80)
site2 (site2.myschool.edu, port 80)
they are listed in that order in the GUI, all are active, each has a separate access and error log and separate document roots.
Any request to either the naked IP address of the machine, or to the domain names for the second and third site are showing the content from the first default site. The log files for the second two are not being written to, and the index files for the second two are not showing. It appears that the first virtual host is masking the other two.
I've tried re-ordering to place the default last, but whatever I do, the first vhost listed masks the other two.
Any ideas what might be going wrong here? All the configuration was done through the Server Admin GUI, so I haven't been mucking about with the on-disk conf files in /etc/httpd
Thanks in advance for any ideas.
Cris

Check the aliases tab for each site and make sure none of the contain a *
The * says match all hostnames, so Apache won't bother looking for additional sites if it finds one.

Wiki and virtual hosts

Is there any way to limit the visibility of group wikis when using virtual hosts? Let me explain...
We have two public sub-domains that map to two virtual hosts on a single Leopard server box:
site1.example.com
site2.example.com
Each site has it's own wiki that is up and running just fine.
The problem is when we visit
site1.example.com/groups
we see the wikis for both site1 and site2 listed. When we click site1 we get through to the site1 wiki. When we click site2, we get a file not found error. The opposite happen when we visit site.example.com/groups.
What I'd really like is for site1.example.com/groups to only list the site1 wiki and site2.example.com/groups to only list the site2 wiki.
Is this possible?

I managed to do this by a 'cheap and nasty' method!
The group listing is created by the file
/usr/share/wikid/lib/appletemplates/grouplisting.xsl
it is the ONLY xsl file that cannot be overridden by a custom wikitheme, but it can be edited.
Within this file you will find an unordered list,
<ul class="contentlist">
</ul >
if you replace this by
<ul class="contentlist">
<script type="text/javascript">
if(location.hostname=='www.foobar1.com'||location.hostname=='foobar1.com')
document.write('<li><a href="http://www.foobar1.com/groups/group_name1/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title1A website that ...</a></li>');
document.write('<li><a href="http://www.foobar1.com/groups/groupname2/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title2Another website </a></li>');
document.write('<li><a href="http://www.foobar1.com/groups/groupname3/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title3A final website .</a></li>');
else if(location.hostname=='www.foobar2.com'||location.hostname=='foobar2.com')
document.write('<li><a href="http://www.foobar2.com/groups/group_name4/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title4 The Home site of </a></li>');
document.write('<li><a href="http://www.foobar2.com/groups/group_name5/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title5An online t;/span></a></li>');
else
document.write('<li><a href="http://www.foobar3.info/groups/group_name6/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title6 The Home site .</a></li>');
document.write('<li><a href="http://www.foobar3.info/groups/group_name7/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title7A wiki for .</a></li>');
</script>
</ul>
Save and restart the webserver from within serveradmin and it should appear.
OK, so it doesn't automatically respond to new groups as you create them but it's easily updated and, if you follow the instructions from a thread I started on wiki_entry tags you COULD update it from within an admin wiki
I don't claim it's pretty, or that it will survive apple's update once they have sorted out their inability to cope with virtual hosting, but it works.

Virtual hosts all redirect to first in list - Snow Leopard Server

I know this is something that's been talked about here before, but I don't see the answer that's making it work for me.
Basically, I am trying to use virtual hosts in a pretty standard fare way. I'm just making a bunch of subdomains: wiki.mysite.com, client1.mysite.com, client2.mysite.com, you get it.
All of these resolve fine, but they're all showing wiki.mysite.com (the first in the list in Server Admin). If I reorder the list, I get whatever's first. I do not have a * in the aliases section of any of these sites.
Can anyone help?

Server manager and workgroup manager in some cases (apache) reads and writes out to files, so you can check if SM is doing the right thing by apache if you go to the actual files in /etc/apache2/sites and check what is there...
i DID have this behavior and fixed it by putting something in the alias part of server manager - i guess it is worth a try and you can always take it out again.

Mailman - trouble creating a second list at an existing virtual host

I have a Virtual Alias error problem ...
I have a Mailman list working (for months) ... *discuss at lists.MLDfamily.org*. I've just created a new list ... *discuss-adults at lists.MLDfamily.org*. The web interface works fine for the new list and it shows lists.MLDfamily.org as its host_name.
+http://lists.mldfamily.org/mailman/admin/discuss-adults+
Both lists show up when I run the following command:
/usr/share/mailman/bin/list_lists -V lists.MLDfamily.org
But deliveries to the Postfix mail server nets me this error on my local server (i.e. the email is making it fine to my server):
Nov 28 11:44:11 darcee postfix/smtpd[11450]: NOQUEUE: reject: RCPT from mail-pv0-f170.google.com[74.125.83.170]: 550 5.1.1 <[email protected]>: *Recipient address rejected: User unknown in virtual alias table*; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-pv0-f170.google.com>
Deliveries to the initial discuss list at this virtual domain continue to work but discuss-adults give the virtual alias table error.
What do I need to do to get this new list into the virtual domain table? I am thinking I am overlooking the obvious - your help is appreciated.
Thanks in advance, Dean
FWIW, this is the process I used to create the list:
(did not need to create the virtual domain since it already existed)
Stopped the mail server using server admin
sudo /usr/share/mailman/bin/rmlist -a discuss-adults +(to remove all residual old list stuff)+
sudo /usr/share/mailman/bin/newlist discuss-adults
sudo /usr/share/mailman/bin/list_lists +new list showed up+
sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org +new list did not show up+
sudo /usr/share/mailman/bin/withlist -l -r fix_url discuss-adults -u lists.MLDfamily.org
sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org +new list now shows up at the proper virtual domain+
sudo /usr/share/mailman/bin/genaliases
sudo postfix reload +failed since mail server was stopped+
started mail server using server admin
To confirm the updates of the virtual alias table I did the following:
ls -l /var/mailman/data +aliases, aliases.db, virtual-mailman, & virtual-mailman.db all were time stamped the last few minutes+
Looking inside aliases and virtual-mailman conformed the proper entries. Aliases and virtual-mailman both contained the following stanzas (in addition to others):
~~
+# STANZA START: discuss+
+# CREATED: Sun Nov 28 11:39:09 2010+
+discuss: "|/usr/share/mailman/mail/mailman post discuss"+
+discuss-admin: "|/usr/share/mailman/mail/mailman admin discuss"+
+discuss-bounces: "|/usr/share/mailman/mail/mailman bounces discuss"+
+discuss-confirm: "|/usr/share/mailman/mail/mailman confirm discuss"+
+discuss-join: "|/usr/share/mailman/mail/mailman join discuss"+
+discuss-leave: "|/usr/share/mailman/mail/mailman leave discuss"+
+discuss-owner: "|/usr/share/mailman/mail/mailman owner discuss"+
+discuss-request: "|/usr/share/mailman/mail/mailman request discuss"+
+discuss-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss"+
+discuss-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss"+
+# STANZA END: discuss+
~~
+# STANZA START: discuss-adults+
+# CREATED: Sun Nov 28 11:39:10 2010+
+discuss-adults: "|/usr/share/mailman/mail/mailman post discuss-adults"+
+discuss-adults-admin: "|/usr/share/mailman/mail/mailman admin discuss-adults"+
+discuss-adults-bounces: "|/usr/share/mailman/mail/mailman bounces discuss-adults"+
+discuss-adults-confirm: "|/usr/share/mailman/mail/mailman confirm discuss-adults"+
+discuss-adults-join: "|/usr/share/mailman/mail/mailman join discuss-adults"+
+discuss-adults-leave: "|/usr/share/mailman/mail/mailman leave discuss-adults"+
+discuss-adults-owner: "|/usr/share/mailman/mail/mailman owner discuss-adults"+
+discuss-adults-request: "|/usr/share/mailman/mail/mailman request discuss-adults"+
+discuss-adults-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss-adults"+
+discuss-adults-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss-adults"+
+# STANZA END: discuss-adults+

The solution came from Mark Shapiro in another forum. In short - always use lower case.
ds
+It should happen automatically. I suspect it didn't in your case+
+because of certain case-sensitivities which are really bugs. If you+
+make all your domain names in mm_cfg.py, i.e. DEFAULTURLHOST,+
+DEFAULTEMAILHOST, additional domains in add_virtualhost() and+
+domains in POSTFIXSTYLE_VIRTUALDOMAINS, all lower case and use all+
+lower case in -u options to newlist or fix_url. Everything should work.+
+The underlying bug is that domains in add_virtualhost() directives are+
+lower-cased by Mailman but are matched case-sensitively to+
+POSTFIXSTYLE_VIRTUALDOMAINS so if the POSTFIXSTYLE_VIRTUALDOMAINS+
+domains are mixed or upper case, they don't match.+
+If you make everything lower case and run fix_url with a lower case -u+
+domain and then run genaliases, you should be OK.+

How to create a new virtual host under tomcat 4.1.x?

hi all
i need some help creating a new virtual host under tomcat 4.1.18!
that's what i do:
i'm using the web configuration, reacheable by typing "http://localhost:8080" and then clickign administration
i create a new host
name: www.class-site.it
application base: webapps\class-site
then i create the context:
document base: webapps\class-site
path: /
and nothing works!!!
anyone could help me?
if needed i can also post the server.xml file
thanx in advance for your help
sandro

It should look like this
<Host name="myvhost.com" debug="0" appbase="/my/path/to/webapps" unpackWars="true">
<Context path ="" docBase="ROOT" debug="0"/>
</Host>
This should be inside the <Engine> tags. You should be able to access a page by going to
http://myvhost.com:8080/index.jsp
Obviously you need index.jsp in /my/path/to/webapps/ROOT/index.jsp
Hope that helps

Wiki listed under other virtual hosts

Similar Messages

Maybe you are looking for