I've mirrored a copy of the AOLserver Wiki onto dev.aolserver.com:
http://dev.aolserver.com/
It's based on a backup of the wiki from about 30 minutes ago. I've
tested it and everything still works except for a few extensions I've
added, which I'm still troubleshooting.
For now, the copy of the AOLserver Wiki up on dev.aolserver.com is in
read-only mode to prevent folks from making changes there that will get
clobbered by a future refresh.
I'd like to make dev.aolserver.com the permanent home of the AOLserver
Wiki, but I want to let it "burn in" for a bit, first. I'd like to make
sure everything works, it performs well enough, etc.
What do you think?
-- Dossy
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <list...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
I think dev.aolserver.com is a better place to find it, and people will
feel it more like the official wiki, based on the url :)
If it works fine, then I think it's a good change.
Regards,
Juan José
-
Juan José del Río | Comercio online / e-commerce
+34 616 512 340 | juan...@simpleoption.com
Simple Option S.L.
Tel: +34 951 930 122
Fax: +34 952 792 455
http://www.simpleoption.com
On Thu, 2007-12-13 at 09:36 -0500, Dossy Shiobara wrote:
> Everyone,
>
> I've mirrored a copy of the AOLserver Wiki onto dev.aolserver.com:
>
> http://dev.aolserver.com/
>
> It's based on a backup of the wiki from about 30 minutes ago. I've
> tested it and everything still works except for a few extensions I've
> added, which I'm still troubleshooting.
>
> For now, the copy of the AOLserver Wiki up on dev.aolserver.com is in
> read-only mode to prevent folks from making changes there that will get
> clobbered by a future refresh.
>
> I'd like to make dev.aolserver.com the permanent home of the AOLserver
> Wiki, but I want to let it "burn in" for a bit, first. I'd like to make
> sure everything works, it performs well enough, etc.
>
> What do you think?
>
> -- Dossy
>
--
janine
I was reading some discussion in AOL mail group on memcached & Bas pointed
out the http://www.outoforder.cc/projects/libs/apr_memcache/ as his choice
for AOLserver to use it a proper module that exposes Tcl commands (which
sounds good to me). Do we have any one who has started working on that or is
there any thing which gives the starting point to work on? Because I am new
to this world (AOL + TCL world) so looking some where to hook myself in
order to make some progress.
Same kind of discussion was also going on
http://openacs.org/forums/message-view?message_id=285980 & the person tried
to make the TCL API but that link is broken so I didn't get any thing from
there as well :(.
I found one more thing which is called "Accessing C library functions using
Critcl" http://wiki.tcl.tk/11227 so thought that I should start using this
library for memcached but confused, so don't know to which way should I go
but in the end my goal is to use memcache functions in TCL scripts.
Thanks.
Regards,
Majid
> I was reading some discussion in AOL mail group on memcached & Bas pointed
> out the http://www.outoforder.cc/projects/libs/apr_memcache/ as his choice
> Same kind of discussion was also going on
> http://openacs.org/forums/message-view?message_id=285980 & the person tried
Vlad Seryakov wrote a nsmemcache module for Naviserver which can
probably be ported to work in AOLserver too with modest effort:
http://openacs.org/forums/message-view?message_id=604828
I've never used any of these, but if I needed memcached support from
AOLserver, I'd probably try, in this order:
1. Vlad's nsmemcache first.
2. Write my a Tcl interface to apr_memcache or whatever other existing
C code API looks good.
3. Finally, if I wasn't happy with any of those, implement the
memcache protocol myself from scratch, in Tcl and/or C.
> I found one more thing which is called "Accessing C library functions using
> Critcl" http://wiki.tcl.tk/11227 so thought that I should start using this
> library for memcached but confused,
I haven't tried CriTcl either, but I don't see any particular benefit
to using it for this.
--
Andrew Piskorski <a...@piskorski.com>
http://www.piskorski.com/
> 2. Write my a Tcl interface to apr_memcache or whatever other existing
> C code API looks good.
That has the advantage of having a mature advanced library (dynamic
server add/remove, pooling) but the good ones all seem to use more
external dependencies that I'd like.
> 3. Finally, if I wasn't happy with any of those, implement the
> memcache protocol myself from scratch, in Tcl and/or C.
The only downside I see to Tcl is that it is hard (impossible?) to do
pooling, creating more network overhead on both the client and the
memcached. C will probably be the best bet.
So my preference would be Vlad's module too right now. In fact, I'll
probably have a play with it soon as I do have an actual use for it
myself now.
Cheers,
Bas.
I'm trying to make mediawiki work on AOLServer 4.5.0 + PostgreSQL 8.1
and I'm facing some problems I didn't expect. I've managed to configure
the connection Ok, but everytime I try to access the Start Page i see
this error in my log:
[07/Jul/2008:10:33:55][29593.3062295472][-conn:0-] Error: fastpath:
stat(/var/lib/aolserver/mediawiki/index.php/Página_principal) failed:
Not a
directory
[07/Jul/2008:10:33:58][29593.3062295472][-conn:0-] Error: fastpath:
stat(/var/lib/aolserver/mediawiki/index.php/Página_principal) failed:
Not a
directory
Can somebody help me on that? This is my configuration file:
#---------------------------------------------------------------------
# change to 80 and 443 for production use
set httpport 8004
set httpsport 443
# If setting port below 1024 with AOLServer 4, read comments in file:
# /var/lib/aolserver/service0/packages/etc/daemontools/run
# The hostname and address should be set to actual values.
# setting the address to 0.0.0.0 means aolserver listens on all
interfaces
set hostname [ns_info hostname]
#set address [ns_info address]
set address 192.168.6.35
# Note: If port is privileged (usually < 1024), OpenACS must be
# started by root, and, in AOLserver 4, the run script have a
# '-b address' flag which matches the address according to settings
(above)
set server "mediawiki"
set servername "Wiki do laboratório de Cluster"
set serverroot "/var/lib/aolserver/${server}"
#---------------------------------------------------------------------
# if debug is false, all debugging will be turned off
set debug false
set homedir /usr/local/aolserver
set bindir [file dirname [ns_info nsd]]
set max_file_upload_mb 60
set max_file_upload_min 10
######################################################################
#
# End of instance-specific settings
#
# Nothing below this point need be changed in a default install.
#
######################################################################
set home [file dirname [ns_info config]]
set pageRoot ${serverroot}
ns_section "ns/parameters"
ns_param serverlog ${serverroot}/log/error.log
ns_param logroll on
ns_param home $homedir
ns_param logdebug true
# setting to Unicode by default
# see http://dqd.com/~mayoff/encoding-doc.html
ns_param HackContentType 1
ns_param DefaultCharset utf-8
ns_param HttpOpenCharset utf-8
ns_param OutputCharset utf-8
ns_param URLCharset utf-8
ns_section "ns/mimetypes"
# Note: AOLserver already has an exhaustive list of MIME types:
#
see: /usr/local/src/aolserver-4.{version}/aolserver/nsd/mimetypes.c
# but in case something is missing you can add it here.
#ns_param default "*/*"
#ns_param .adp "text/html; charset=iso-8859-1"
ns_param Default text/plain
ns_param NoExtension text/plain
ns_param .pcd image/x-photo-cd
ns_param .prc application/x-pilot
ns_param .xls application/vnd.ms-excel
ns_param .doc application/vnd.ms-word
ns_section "ns/threads"
ns_param mutexmeter true ;# measure lock contention
# The per-thread stack size must be a multiple of 8k for AOLServer
to run under MacOS X
ns_param stacksize [expr 1 * 8192 * 256]
ns_section "ns/servers"
ns_param $server $servername
ns_section ns/server/${server}
ns_param directoryfile
"index.htm,index.html,index.adp,index.php"
ns_param pageroot $pageRoot
ns_param maxthreads 20
ns_param minthreads 5
ns_param maxconns 100
ns_param urlcharset "utf-8"
ns_param outputcharset "utf-8"
ns_param inputcharset "utf-8"
ns_section ns/server/${server}/adp
ns_param map "/*.adp"
#
# PHP
#
ns_section ns/server/${server}/module/php
ns_param map "/*.php"
ns_section ns/server/${server}/modules
ns_param nssock ${bindir}/nssock.so
ns_param nslog ${bindir}/nslog.so
ns_param nssha1 ${bindir}/nssha1.so
ns_param nscache ${bindir}/nscache.so
ns_param php ${bindir}/libphp5.so
ns_param nsdb ${bindir}/nsdb.so
ns_section ns/server/${server}/module/nssock
ns_param timeout 120
ns_param address $address
ns_param hostname $hostname
ns_param port $httpport
# setting maxinput higher than practical may leave the server
vulnerable to resource DoS attacks
# see http://www.panoptic.com/wiki/aolserver/166
ns_param maxinput [expr $max_file_upload_mb * 1024 *
1024] ; #Maximum File Size for uploads in bytes
ns_param maxpost [expr $max_file_upload_mb * 1024 *
1024] ; #Maximum File Size for uploads in bytes
ns_param recvwait [expr $max_file_upload_min * 60] ;#
Maximum request time in minutes
#---------------------------------------------------------------------
#
# Access log -- nslog
#
#---------------------------------------------------------------------
ns_section ns/server/${server}/module/nslog
ns_param debug false
ns_param dev false
ns_param enablehostnamelookup false
ns_param file ${serverroot}/log/${server}.log
ns_param logcombined true
ns_param extendedheaders X-User-Id
# ns_param logrefer false
# ns_param loguseragent false
# ns_param logreqtime true
ns_param maxbackup 1000
ns_param rollday *
ns_param rollfmt %Y-%m-%d-%H:%M
ns_param rollhour 0
ns_param rollonsignal true
ns_param rolllog true
For those of you who remember that technology, is it possible to configure
it to serve multiple domains (say www.foo.com and www.bar.com) so that users
of each domain think they are on a site dedicated to that respective domain?
Best would be to have each domain resolve to the same IP address. I'm
comfortable making changes to the core tcl code handling security and the
connections.
Does anyone know whether this is possible, and broadly how to do it? Thanks
very much!
Dave Siktberg
using a rewrite filter: http://rmadilo.com/files/nsrewrite/
or something along the lines of ACS with abstract filename handling:
VAT (Virtual hosting, Abstract file handling, Templating):
This is ancient code, but I still use VAT in a similar situation as you,
VAT was, at the time, a little more advanced than the ACS request
processor.
Note that you can also run a regular proxy server on your forward IP and
configure several AOLserver instances on internal ports, but VAT is
helpful when there is a lot of shared code that evolves along an
identical path.
tom jackson
http://rmadilo.com/files/vat/index.html
tom jackson
On Mon, 2008-07-07 at 08:01 -0700, Tom Jackson wrote:
> or something along the lines of ACS with abstract filename handling:
>
> VAT (Virtual hosting, Abstract file handling, Templating):
>
> http://rmadilo.com/files/vat/
Well, as far as I have seen, you've mapped .php files to PHP, but the
url you're giving us is not finished in .php , so maybe that's the
reason why php is not working correctly.
Put a file with "test.php" as name in a directory with some php code,
and see if it gets executed correctly. If it gets executed correctly,
then it's a problem with the reason I told you above, very probably.
Regards,
Juan José
-
Juan José del Río |
(+34) 616 512 340 | juan...@simpleoption.com
Simple Option S.L.
Tel: (+34) 951 930 122
Fax: (+34) 951 930 122
http://www.simpleoption.com
On Thu, 2008-07-10 at 08:30 -0300, Eduardo Santos - Novo telefone:
8148-6611 wrote:
> No help on that?
>
> 2008/7/7, Eduardo Santos <eduardo....@gmail.com>:
> Hi everibody,
>
> I'm trying to make mediawiki work on AOLServer 4..5.0 +
Add this to the end of your main config file to print out the results:
set configDebug 1
if {[info exists configDebug] && $configDebug} {
set sections [ns_configsections]
set output [list]
foreach section $sections {
set name [ns_set name $section]
set section_txt ""
append section_txt "ns_section $name\n"
set size [ns_set size $section]
for {set i 0} {$i < $size} {incr i} {
append section_txt "\t[list ns_param [ns_set key $section $i]
[ns_set value $section $i]]\n"
}
lappend output $section_txt
}
set output "[join [lsort $output] "\n"]\n"
puts "\n$output\n"
}
This should print out your config to your error file, after a restart,
before any other log messages for the restart.
Post the result here.
tom jackson
On Thu, 2008-07-10 at 08:30 -0300, Eduardo Santos - Novo telefone:
8148-6611 wrote: