You can subscribe to this list here.
2005 |
Jan
|
Feb
(53) |
Mar
(62) |
Apr
(88) |
May
(55) |
Jun
(204) |
Jul
(52) |
Aug
|
Sep
(1) |
Oct
(94) |
Nov
(15) |
Dec
(68) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(130) |
Feb
(105) |
Mar
(34) |
Apr
(61) |
May
(41) |
Jun
(92) |
Jul
(176) |
Aug
(102) |
Sep
(247) |
Oct
(69) |
Nov
(32) |
Dec
(140) |
2007 |
Jan
(58) |
Feb
(51) |
Mar
(11) |
Apr
(20) |
May
(34) |
Jun
(37) |
Jul
(18) |
Aug
(60) |
Sep
(41) |
Oct
(105) |
Nov
(19) |
Dec
(14) |
2008 |
Jan
(3) |
Feb
|
Mar
(7) |
Apr
(5) |
May
(123) |
Jun
(5) |
Jul
(1) |
Aug
(29) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(3) |
2009 |
Jan
|
Feb
(36) |
Mar
(29) |
Apr
|
May
|
Jun
(7) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
|
Nov
(13) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
(9) |
Apr
(11) |
May
(16) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(92) |
Nov
(28) |
Dec
(16) |
2013 |
Jan
(9) |
Feb
(2) |
Mar
|
Apr
(4) |
May
(4) |
Jun
(6) |
Jul
(14) |
Aug
(12) |
Sep
(4) |
Oct
(13) |
Nov
(1) |
Dec
(6) |
2014 |
Jan
(23) |
Feb
(19) |
Mar
(10) |
Apr
(14) |
May
(11) |
Jun
(6) |
Jul
(11) |
Aug
(15) |
Sep
(41) |
Oct
(95) |
Nov
(23) |
Dec
(11) |
2015 |
Jan
(3) |
Feb
(9) |
Mar
(19) |
Apr
(3) |
May
(1) |
Jun
(3) |
Jul
(11) |
Aug
(1) |
Sep
(15) |
Oct
(5) |
Nov
(2) |
Dec
|
2016 |
Jan
(7) |
Feb
(11) |
Mar
(8) |
Apr
(1) |
May
(3) |
Jun
(17) |
Jul
(12) |
Aug
(3) |
Sep
(5) |
Oct
(19) |
Nov
(12) |
Dec
(6) |
2017 |
Jan
(30) |
Feb
(23) |
Mar
(12) |
Apr
(32) |
May
(27) |
Jun
(7) |
Jul
(13) |
Aug
(16) |
Sep
(6) |
Oct
(11) |
Nov
|
Dec
(12) |
2018 |
Jan
(1) |
Feb
(5) |
Mar
(6) |
Apr
(7) |
May
(23) |
Jun
(3) |
Jul
(2) |
Aug
(1) |
Sep
(6) |
Oct
(6) |
Nov
(10) |
Dec
(3) |
2019 |
Jan
(26) |
Feb
(15) |
Mar
(9) |
Apr
|
May
(8) |
Jun
(14) |
Jul
(10) |
Aug
(10) |
Sep
(4) |
Oct
(2) |
Nov
(20) |
Dec
(10) |
2020 |
Jan
(10) |
Feb
(14) |
Mar
(29) |
Apr
(11) |
May
(25) |
Jun
(21) |
Jul
(23) |
Aug
(12) |
Sep
(19) |
Oct
(6) |
Nov
(8) |
Dec
(12) |
2021 |
Jan
(29) |
Feb
(9) |
Mar
(8) |
Apr
(8) |
May
(2) |
Jun
(2) |
Jul
(9) |
Aug
(9) |
Sep
(3) |
Oct
(4) |
Nov
(12) |
Dec
(13) |
2022 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(12) |
May
(15) |
Jun
(7) |
Jul
(10) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
|
2023 |
Jan
(15) |
Feb
|
Mar
(23) |
Apr
(1) |
May
(2) |
Jun
(10) |
Jul
|
Aug
(22) |
Sep
(19) |
Oct
(2) |
Nov
(20) |
Dec
|
2024 |
Jan
(1) |
Feb
|
Mar
(16) |
Apr
(15) |
May
(6) |
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(18) |
Dec
(6) |
2025 |
Jan
(12) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
(5) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Mike <nee...@gm...> - 2006-07-23 00:04:49
|
> My Fedora box has automake-1.4 automake-1.5 automake-1.6 > automake-1.7 automake-1.9, but it also has plain 'automake', which is > the 1.9 version. > > I guess we need something like: > > $ AUTOMAKE="automake-1.9" ./autogen.sh perhaps autogen.sh could be made to look for automake, then automake-1.9, then automake-1.8, etc... until it found one... I'm not sure this is the right answer, but I guess it's one way to solve the "problem". |
From: Mike <nee...@gm...> - 2006-07-23 00:02:06
|
> > Right now I am > > looking at 4 choices: > > > > 1) drop nsdb from naviserver and use nstcl after cleaning up any > > multi-thread issues > > 2) import ad_proc and 00-database from OACS and hack them up until > > they work. (unfortunately the combination of the two is not possible > > - nstcl ad_proc does not support positional parameters without default > > values after named parameters ith default values) > > 3) dig into OSSWEB and import its notion of ad_proc and db_* > > 4) nsdbi and friends > > > > Numbers 3 and 4 sound most appealing to me at this moment because > > these are "most supported" by the naviserver "community" - getting > > help with 00-database is unlikely to happen for something unrelated to > > OACS and nstcl hasn't been touched in 2+ years. The downside to > > Number 3 is that i need to import a bunch of things with OSSWEB that > > are not related to the database, and I am hesitant about doing so. > > Your thoughts, comments, and opinions are most welcome. > > > You're using Postgres, right? Correct. Thus far I've been trying to use nstk. It hasn't been terrible, but it hasn't been pleasant either... |
From: Stephen D. <sd...@gm...> - 2006-07-20 23:24:30
|
Oops! On 7/18/06, Vlad Seryakov <vl...@cr...> wrote: > Today i noticed error messages dns: timeout waiting for concurrent update > and found out that in dns.c timeout variable is never setup, > so i guess it is random value or 0 and then or subsecond timeouts in dns > resolving. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > |
From: Stephen D. <sd...@gm...> - 2006-07-20 22:57:13
|
On 7/17/06, Mike <nee...@gm...> wrote: > On 7/17/06, Stephen Deasey <sd...@gm...> wrote: > > What's the default versions of autoconf and automake on FreeBSD (FreeBSD x.x?) > > > > What did the default autoconf not like in our configure script? > > Stephen, > I believe there is no such thing as "default" autoconf in FreeBSD. > It's a third-party package, and multiple versions of it are available > because various other things rely on a particular version, so the > version is tacked on at the end... A similar thing is done with tcl - > there is no "tclsh" on FreeBSD, only tclsh8.4 or tclsh8.5, for > example.. (someone please correct me if I am wrong... - perhaps there > is a port of some "compatibility" shim that finds latest version and > tries it that I am unaware of). > My Fedora box has automake-1.4 automake-1.5 automake-1.6 automake-1.7 automake-1.9, but it also has plain 'automake', which is the 1.9 version. I guess we need something like: $ AUTOMAKE="automake-1.9" ./autogen.sh then? |
From: Stephen D. <sd...@gm...> - 2006-07-20 22:54:40
|
On 7/17/06, Mike <nee...@gm...> wrote: > On 7/17/06, Stephen Deasey <sd...@gm...> wrote: > > I have a new database module called nsdbi which presents an API > > inspired by the ACS db procs. It's all built right into the driver > > framework. > > > > The nsdb module doesn't know anything about bind variable. The > > nspostgres driver *emulates* bind variables. The ACS procs provide a > > unified interface over the custom postgres and oracle drivers. > > > > For nsdbi I added bind variable support to the driver interface and > > native postgres support to the nsdbipg driver. > > > > It isn't just bind variable though. There are a few things in nsdb, > > and some in the nsdb/acs combo that are less than ideal. And there's > > some opportunities for new stuff: prepared queres, caching, > > performance hacks etc. > > > > I'll try and upload this to naviserver cvs soon as the basics seem to > > be working. It's dependent on Tcl 8.5 dicts, but 8.5 seems to be > > taking forever to release so I'm going to remove that. Might as well > > get it out there in whatever state so folks can bash on it. > > Stephen, > Two things. First, I think that removing the dict stuff is a > mistake. Reverting any work that was progress is not a good idea. It's not a problem. I have it in CVS on my laptop. Needs to be done anyway -- I want to run it and not depend on unreleased Tcl 8.5. > Second, I would love to help at least test this module or further its > progress. However, I need for this to happen <now> - as in, at the > latest by tomorrow evening EDT I will need to have at least something > I can use to access the database from naviserver. \ Sorry, missed this. I'm syncing the laptop every few days... > Right now I am > looking at 4 choices: > > 1) drop nsdb from naviserver and use nstcl after cleaning up any > multi-thread issues > 2) import ad_proc and 00-database from OACS and hack them up until > they work. (unfortunately the combination of the two is not possible > - nstcl ad_proc does not support positional parameters without default > values after named parameters ith default values) > 3) dig into OSSWEB and import its notion of ad_proc and db_* > 4) nsdbi and friends > > Numbers 3 and 4 sound most appealing to me at this moment because > these are "most supported" by the naviserver "community" - getting > help with 00-database is unlikely to happen for something unrelated to > OACS and nstcl hasn't been touched in 2+ years. The downside to > Number 3 is that i need to import a bunch of things with OSSWEB that > are not related to the database, and I am hesitant about doing so. > Your thoughts, comments, and opinions are most welcome. > You're using Postgres, right? |
From: Vlad S. <vl...@cr...> - 2006-07-18 00:05:41
|
Today i noticed error messages dns: timeout waiting for concurrent update and found out that in dns.c timeout variable is never setup, so i guess it is random value or 0 and then or subsecond timeouts in dns resolving. |
From: Mike <nee...@gm...> - 2006-07-17 21:42:32
|
On 7/17/06, Stephen Deasey <sd...@gm...> wrote: > What's the default versions of autoconf and automake on FreeBSD (FreeBSD x.x?) > > What did the default autoconf not like in our configure script? Stephen, I believe there is no such thing as "default" autoconf in FreeBSD. It's a third-party package, and multiple versions of it are available because various other things rely on a particular version, so the version is tacked on at the end... A similar thing is done with tcl - there is no "tclsh" on FreeBSD, only tclsh8.4 or tclsh8.5, for example.. (someone please correct me if I am wrong... - perhaps there is a port of some "compatibility" shim that finds latest version and tries it that I am unaware of). |
From: Mike <nee...@gm...> - 2006-07-17 21:39:10
|
On 7/17/06, Stephen Deasey <sd...@gm...> wrote: > I have a new database module called nsdbi which presents an API > inspired by the ACS db procs. It's all built right into the driver > framework. > > The nsdb module doesn't know anything about bind variable. The > nspostgres driver *emulates* bind variables. The ACS procs provide a > unified interface over the custom postgres and oracle drivers. > > For nsdbi I added bind variable support to the driver interface and > native postgres support to the nsdbipg driver. > > It isn't just bind variable though. There are a few things in nsdb, > and some in the nsdb/acs combo that are less than ideal. And there's > some opportunities for new stuff: prepared queres, caching, > performance hacks etc. > > I'll try and upload this to naviserver cvs soon as the basics seem to > be working. It's dependent on Tcl 8.5 dicts, but 8.5 seems to be > taking forever to release so I'm going to remove that. Might as well > get it out there in whatever state so folks can bash on it. Stephen, Two things. First, I think that removing the dict stuff is a mistake. Reverting any work that was progress is not a good idea. Second, I would love to help at least test this module or further its progress. However, I need for this to happen <now> - as in, at the latest by tomorrow evening EDT I will need to have at least something I can use to access the database from naviserver. Right now I am looking at 4 choices: 1) drop nsdb from naviserver and use nstcl after cleaning up any multi-thread issues 2) import ad_proc and 00-database from OACS and hack them up until they work. (unfortunately the combination of the two is not possible - nstcl ad_proc does not support positional parameters without default values after named parameters ith default values) 3) dig into OSSWEB and import its notion of ad_proc and db_* 4) nsdbi and friends Numbers 3 and 4 sound most appealing to me at this moment because these are "most supported" by the naviserver "community" - getting help with 00-database is unlikely to happen for something unrelated to OACS and nstcl hasn't been touched in 2+ years. The downside to Number 3 is that i need to import a bunch of things with OSSWEB that are not related to the database, and I am hesitant about doing so. Your thoughts, comments, and opinions are most welcome. |
From: Stephen D. <sd...@gm...> - 2006-07-17 20:37:26
|
What's the default versions of autoconf and automake on FreeBSD (FreeBSD x.x?) What did the default autoconf not like in our configure script? On 7/16/06, Mike <nee...@gm...> wrote: > The following patch is needed to get naviserver CVS to build on > FreeBSD... Almost certainly this is not something to commit, but in > case someone comes across this post, it'll save them 10 minutes... > (or someone will point out to me that there's an easier way :) ) > > Index: autogen.sh > =================================================================== > RCS file: /cvsroot/naviserver/naviserver/autogen.sh,v > retrieving revision 1.1 > diff -r1.1 autogen.sh > 15c15 > < (autoconf --version) < /dev/null > /dev/null 2>&1 || { > --- > > (autoconf259 --version) < /dev/null > /dev/null 2>&1 || { > 17c17 > < echo "**Error**: You must have \`autoconf' installed." > --- > > echo "**Error**: You must have \`autoconf259' installed." > 23c23 > < (automake --version) < /dev/null > /dev/null 2>&1 || { > --- > > (automake19 --version) < /dev/null > /dev/null 2>&1 || { > 25c25 > < echo "**Error**: You must have \`automake' installed." > --- > > echo "**Error**: You must have \`automake19' installed." > 31,32c31,32 > < # if no automake, don't bother testing for aclocal > < test -n "$NO_AUTOMAKE" || (aclocal --version) < /dev/null > > /dev/null 2>&1 || { > --- > > # if no automake19, don't bother testing for aclocal19 > > test -n "$NO_AUTOMAKE" || (aclocal19 --version) < /dev/null > /dev/null 2>&1 || { > 34c34 > < echo "**Error**: Missing \`aclocal'. The version of \`automake'" > --- > > echo "**Error**: Missing \`aclocal19'. The version of \`automake19'" > 36c36 > < echo "You can get automake from ftp://ftp.gnu.org/pub/gnu/" > --- > > echo "You can get automake19 from ftp://ftp.gnu.org/pub/gnu/" > 46,47c46,47 > < echo "Running aclocal -I m4 $ACLOCAL_FLAGS" > < aclocal -I m4 $ACLOCAL_FLAGS || exit $? > --- > > echo "Running aclocal19 -I m4 $ACLOCAL_FLAGS" > > aclocal19 -I m4 $ACLOCAL_FLAGS || exit $? > 49,50c49,50 > < echo "Running autoheader" > < autoheader || exit $? > --- > > echo "Running autoheader259" > > autoheader259 || exit $? > 52,53c52,53 > < echo "Running autoconf" > < autoconf || exit $? > --- > > echo "Running autoconf259" > > autoconf259 || exit $? > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > |
From: Stephen D. <sd...@gm...> - 2006-07-17 20:34:48
|
On 7/16/06, Mike <nee...@gm...> wrote: > [lumping into one mail since it looks like we have a pretty tightly > knit group of readers anyway] > > the sample nscgi config should read: > ns_param map "GET /cgi-bin ${homedir}/cgi-bin" > instead of hardcoing the path... > > what is the "right" way of getting nsposgres to build and run under > naviserver? nspostgres was not in cvs for either naviserver or the > modules - i found it on sourceforge and had to hack it a bit to get it > to build even (in particular, it wants the _3_PlUS define removed in: > 2005-07-30 Stephen Deasey <sd...@us...> > > * include/ns.h: Untabify and reformat some definitions. Remove > unused/unneeded NS_AOLSERVER_3_PLUS, NS_SHUTDOWN and > NS_REGISTER_SERVER_TRACE. > )... > > now, if there is no less painful way to get nspostgres to work... > there should be... :) overall, the state of what modules exist and > how to use them appears to be... abysmal. or am I just looking into > the wrong place? > The nspostgres module was imported into naviserver cvs and renamed nsdbpg. All the database module were renamed nsdb* to prevent confusion when a new db interface module is imported... (see below) > another question I have is about the ns_db... the OpenACS database > access functions are quite nice - is there some way to get them under > NaviServer without having to hack up OpenACS and extract them out of > it? I know there is an nstcl package available on sourceforge that > reimplements this functionality, but from a mile-high guess, this > package will conflict/not play nice with the NaveServer stuff... > I have a new database module called nsdbi which presents an API inspired by the ACS db procs. It's all built right into the driver framework. The nsdb module doesn't know anything about bind variable. The nspostgres driver *emulates* bind variables. The ACS procs provide a unified interface over the custom postgres and oracle drivers. For nsdbi I added bind variable support to the driver interface and native postgres support to the nsdbipg driver. It isn't just bind variable though. There are a few things in nsdb, and some in the nsdb/acs combo that are less than ideal. And there's some opportunities for new stuff: prepared queres, caching, performance hacks etc. I'll try and upload this to naviserver cvs soon as the basics seem to be working. It's dependent on Tcl 8.5 dicts, but 8.5 seems to be taking forever to release so I'm going to remove that. Might as well get it out there in whatever state so folks can bash on it. |
From: Stephen D. <sd...@gm...> - 2006-07-17 20:14:43
|
Upload your SSH key... On 7/17/06, Bernd Eidenschink <eid...@we...> wrote: > > I have access now after resetting the password, maybe you too: > > > Posted By: burley > Date: 2006-07-14 04:41 > Summary: Password expiry due to shell server exploit > > A recent kernel exploit was released that allowed a non admin user to escalate > privileges on the host pr-shell1. We urge all users who frequent this host to > change their password immediately and check their project group space for any > tampering. As a precaution, we have blocked access to all project resources > by password until the user resets their password. After the password has been > reset, project resources should be accessible within 5 minutes. > |
From: Bernd E. <eid...@we...> - 2006-07-17 15:20:39
|
Hi Mike, > ns_section "ns/server/server1/pool/fast" > should probably be > ns_section "ns/server/${servername}/pool/fast" thats true. > mimetypes.tcl is not sourced the binary has a lot of types compiled for the start, see nsd/mimetypes.c. the "mimetypes.tcl" from the contrib dir can be optionally sourced. > nscp and nsadmin are enabled by default with known passwords? yes, should be changed, imho. > it's also almost entirely unclear which modules are needed/do what... usually you should be fine with nssock and nslog. the others could be commented out. > perhaps tcl/ directory is always sourced in its entirety - but then > what are "Tcl modules" mentioned in sample config? There is the private (per-virtual-server) Tcl modules directory ns_section "ns/server/servername/tcl" ns_param library PATH/modules/tcl The [ns_library private] command will return that. Shared modules are returned via [ns_library shared] and configured: ns_section "ns/parameters" ns_param tcllibrary PATH/tcl The mentioned "Tcl modules" are loaded via 'ns_ictl addmodule' (for virtual-servers), but others may comment why this was implemented. > It would be amazingly useful if the configuration section of the wiki > was available or at least some pointer to another document existed > somewhere... i'm currently experimenting with a layout like this: # Logical configuration units are separated into different sub-configuration # files and included here. # # Legend: (c) change before first use # # nsd.conf # | # |-- global.conf (c) # |-- uid.conf (c) # |-- listen.conf (c) # |-- server-tuning.conf # |-- server-log.conf # |-- access-log.conf # |-- mimetypes.conf # |-- i18l.conf # |-- adp.conf # |-- smtp.conf # |-- database.conf # |-- modules.conf # |-- file-caching.conf # |-- control-port.conf # |-- statistics.conf # |-- cgi.conf # | # `--modules.d/ # `-- *.conf # `--vhosts.d/ # `-- *.conf (c) "experimenting", because there's no perfect one-layout-fits-it-all approach and sometimes separation is not that logical. (this one, e.g., may come out to be annoying for someone using lots of virtual hosting (i don't, so it's no problem for me ;-)) as i don't know if you can encapsulate most of the configs to a separate file without breaking the basic concept.) Bernd. |
From: Bernd E. <eid...@we...> - 2006-07-17 06:13:57
|
I have access now after resetting the password, maybe you too: Posted By: burley Date: 2006-07-14 04:41 Summary: Password expiry due to shell server exploit A recent kernel exploit was released that allowed a non admin user to escalate privileges on the host pr-shell1. We urge all users who frequent this host to change their password immediately and check their project group space for any tampering. As a precaution, we have blocked access to all project resources by password until the user resets their password. After the password has been reset, project resources should be accessible within 5 minutes. |
From: Bernd E. <b.e...@ki...> - 2006-07-17 06:00:39
|
> i have implented something similar (xotcl-request monitor) which you > can get from the > oacs cvs (still, xotcl style license). Thanks for the tip! I'll take a look. Bernd. |
From: Mike <nee...@gm...> - 2006-07-16 19:08:58
|
The following patch is needed to get naviserver CVS to build on FreeBSD... Almost certainly this is not something to commit, but in case someone comes across this post, it'll save them 10 minutes... (or someone will point out to me that there's an easier way :) ) Index: autogen.sh =================================================================== RCS file: /cvsroot/naviserver/naviserver/autogen.sh,v retrieving revision 1.1 diff -r1.1 autogen.sh 15c15 < (autoconf --version) < /dev/null > /dev/null 2>&1 || { --- > (autoconf259 --version) < /dev/null > /dev/null 2>&1 || { 17c17 < echo "**Error**: You must have \`autoconf' installed." --- > echo "**Error**: You must have \`autoconf259' installed." 23c23 < (automake --version) < /dev/null > /dev/null 2>&1 || { --- > (automake19 --version) < /dev/null > /dev/null 2>&1 || { 25c25 < echo "**Error**: You must have \`automake' installed." --- > echo "**Error**: You must have \`automake19' installed." 31,32c31,32 < # if no automake, don't bother testing for aclocal < test -n "$NO_AUTOMAKE" || (aclocal --version) < /dev/null > /dev/null 2>&1 || { --- > # if no automake19, don't bother testing for aclocal19 > test -n "$NO_AUTOMAKE" || (aclocal19 --version) < /dev/null > /dev/null 2>&1 || { 34c34 < echo "**Error**: Missing \`aclocal'. The version of \`automake'" --- > echo "**Error**: Missing \`aclocal19'. The version of \`automake19'" 36c36 < echo "You can get automake from ftp://ftp.gnu.org/pub/gnu/" --- > echo "You can get automake19 from ftp://ftp.gnu.org/pub/gnu/" 46,47c46,47 < echo "Running aclocal -I m4 $ACLOCAL_FLAGS" < aclocal -I m4 $ACLOCAL_FLAGS || exit $? --- > echo "Running aclocal19 -I m4 $ACLOCAL_FLAGS" > aclocal19 -I m4 $ACLOCAL_FLAGS || exit $? 49,50c49,50 < echo "Running autoheader" < autoheader || exit $? --- > echo "Running autoheader259" > autoheader259 || exit $? 52,53c52,53 < echo "Running autoconf" < autoconf || exit $? --- > echo "Running autoconf259" > autoconf259 || exit $? |
From: Andrew P. <at...@pi...> - 2006-07-16 13:54:19
|
> > another question I have is about the ns_db... the OpenACS database > > access functions are quite nice - is there some way to get them under > > NaviServer without having to hack up OpenACS and extract them out of > > it? Nope. The right way to do it is to refactor the OpenACS db_* proc support into a stand-alone Tcl package, and then use that same package for both OpenACS and non-OpenACS systems. That definitely is feasible, but unfortunately, I never got around to doing it. :( -- Andrew Piskorski <at...@pi...> http://www.piskorski.com/ |
From: Vlad S. <vl...@cr...> - 2006-07-16 13:16:29
|
Just checkout modules from CVS, it has nsdbpg which compiles and wors just fine. > what is the "right" way of getting nsposgres to build and run under > naviserver? nspostgres was not in cvs for either naviserver or the > modules - i found it on sourceforge and had to hack it a bit to get it > to build even (in particular, it wants the _3_PlUS define removed in: > 2005-07-30 Stephen Deasey <sd...@us...> > > another question I have is about the ns_db... the OpenACS database > access functions are quite nice - is there some way to get them under > NaviServer without having to hack up OpenACS and extract them out of > it? I know there is an nstcl package available on sourceforge that > reimplements this functionality, but from a mile-high guess, this > package will conflict/not play nice with the NaveServer stuff... > > There are some in nstk modules, not like in OpenACS but higher level and small. OACS duplication never was in out TODO list:-)) |
From: Mike <nee...@gm...> - 2006-07-16 08:08:40
|
[lumping into one mail since it looks like we have a pretty tightly knit group of readers anyway] the sample nscgi config should read: ns_param map "GET /cgi-bin ${homedir}/cgi-bin" instead of hardcoing the path... what is the "right" way of getting nsposgres to build and run under naviserver? nspostgres was not in cvs for either naviserver or the modules - i found it on sourceforge and had to hack it a bit to get it to build even (in particular, it wants the _3_PlUS define removed in: 2005-07-30 Stephen Deasey <sd...@us...> * include/ns.h: Untabify and reformat some definitions. Remove unused/unneeded NS_AOLSERVER_3_PLUS, NS_SHUTDOWN and NS_REGISTER_SERVER_TRACE. )... now, if there is no less painful way to get nspostgres to work... there should be... :) overall, the state of what modules exist and how to use them appears to be... abysmal. or am I just looking into the wrong place? another question I have is about the ns_db... the OpenACS database access functions are quite nice - is there some way to get them under NaviServer without having to hack up OpenACS and extract them out of it? I know there is an nstcl package available on sourceforge that reimplements this functionality, but from a mile-high guess, this package will conflict/not play nice with the NaveServer stuff... Thanks for your input... after a few "serious" hours of NaviServer - things look pretty good. At least I think I've found what I was looking for - hopefully you guys won't be too annoyed with all my questions, since I'm likely to have much more of them in the future... |
From: Mike <nee...@gm...> - 2006-07-16 07:09:48
|
ns_section "ns/server/server1/pool/fast" should probably be ns_section "ns/server/${servername}/pool/fast" fastpath section contains: ns_param directoryfile "index.adp index.tcl index.html index.htm" I can only assume index.adp and index.tcl are here in error - otherwise I must be completely confused about "fastpath". mimetypes.tcl is not sourced nscp and nsadmin are enabled by default with known passwords? it's also almost entirely unclear which modules are needed/do what... a bunch of tcl/ modules are shipped, but not included by default in the config - a bunch of bin/*.so modules are shipped, and are included, but probably should be commented out (e.g. nsproxy)... perhaps tcl/ directory is always sourced in its entirety - but then what are "Tcl modules" mentioned in sample config? It would be amazingly useful if the configuration section of the wiki was available or at least some pointer to another document existed somewhere... |
From: Gustaf N. <ne...@wu...> - 2006-07-14 20:20:14
|
Bernd Eidenschink schrieb: > Hi friends, > > "and now to something completely different: the larch"... ;-) > > Some of you might know: > http://www.zdziarski.com/projects/mod_evasive/ > > i have implented something similar (xotcl-request monitor) which you can get from the oacs cvs (still, xotcl style license). a filter redirects all requests to a monitoring thread that decides whether a request should be blocked/throttled/whatever and which keeps various statistics. It deals as well with repeated requests. The key components are not dependent on oacs. We use this since a couple of years on our productive systems, it helped us a lot... greetings -gustaf |
From: Bernd E. <eid...@we...> - 2006-07-14 17:21:47
|
Hi friends, "and now to something completely different: the larch"... ;-) Some of you might know: http://www.zdziarski.com/projects/mod_evasive/ I'm just interested in some theoretical thoughts, if there would be a ns_evasive module... how to set up the "storage": Background (Remember: this is an Apache module): "Detection is performed by creating an internal dynamic hash table of IP Addresses and URIs, and denying any single IP address from any of the following: * Requesting the same page more than a few times per second * Making more than 50 concurrent requests on the same child per second" (It then answers with a HTTP status code of 403 for a specified time) And (from the Apache-view): "This module instantiates for each listener individually [...] Because of this per-child design, legitimate requests are never compromised (even from proxies and NAT addresses) but only scripted attacks. Even a user repeatedly clicking on 'reload' should not be affected unless they do it maliciously." In our Naviserver-world, when storing requests of clients (IP) to objects on the server (whatever you consider a "page", say HTML/ADP; and all the other page elements on the other side), what could a possible plan look like: * do the key/value lookup via NSV arrays? * or thread-locally? Or everything in the first/the latter? If I want to guarantee, say, client X request a page Y only 2 times within 5 seconds, this leads to NSV ("guarantee"). But when I think of e.g. the 70 images referenced in Y... and some of them also referenced from page Y'2 with a browser not caching anything... hm. Is the " legitimate requests are never compromised" promise gained by a "server-wide-blindness" approach, a distribution of storage to the available processes? And would turning on / off keepalive introduce some subtle differences? cu Bernd. |
From: Zoran V. <zv...@ar...> - 2006-07-14 14:20:54
|
Am 14.07.2006 um 16:15 schrieb Vlad Seryakov: > PS: As you see SF issues come back every month with something > different, > usually resulted in no access. Yes, yes... I can read the hidden message... Zoran |
From: Zoran V. <zv...@ar...> - 2006-07-14 14:20:09
|
Am 14.07.2006 um 16:13 schrieb Vlad Seryakov: > I still think that you could build ns_callback command that will be > similar to ns_conn, i.e. it works only in the context of callback like > ns_conn in the connection thread only. This way you can extend it > as you > wish and be backward compatible > Almost! This is what I also thought at the first glance! But when you think deeper... My idea was to add more information available to the callback in particular, the events of adding, calling and removing. BUT, in order to do that you MUST actually call the callback once at the registration, regulary during the execution and once at the de-registration. Now, this can't be easily done as callbacks may have never been designed for such call pattern! Therefore it is not possible to automate this task as I wanted it. If the callbacks are written with this notion (i.e. that they will be called at least 2 times (on registration and de-registration) then it is another story. But since we cannot really know how all this will react, we can't do that. Effectively I can build a kind-of ns_callback command which is valid only in the context of the callback. But for it to be used the callback must be executed(!) and this is where all comes down. Understand? That's why I had to throw this idea away... I gues I was just not thinking enough beforemath (how could I, we have 32 grades centigrade here and we're all sweating our brains out...) Cheers, Zoran |
From: Vlad S. <vl...@cr...> - 2006-07-14 14:13:41
|
Same here, i submited bug to them but i see a lot of such submisions already, so it affected many people. PS: As you see SF issues come back every month with something different, usually resulted in no access. Zoran Vasiljevic wrote: > Hi! > > Aparently, some accounts cannot login to CVS as > they get their password rejected. Same for me as of > today. I do not know how long it will take now... > > Cheers > Zoran > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
From: Vlad S. <vl...@cr...> - 2006-07-14 14:12:11
|
I still think that you could build ns_callback command that will be similar to ns_conn, i.e. it works only in the context of callback like ns_conn in the connection thread only. This way you can extend it as you wish and be backward compatible Zoran Vasiljevic wrote: > Am 13.07.2006 um 22:16 schrieb Stephen Deasey: > >> Why can't you initialise resources when you register the callback? I >> don't think I understand the problem here... > > Well, my first idea was to get a kind of "self-initializing" and > "self-cleaning" procedures. Most importantly the "self-cleaning" > as "self-initializing" is pretty easy to make with kind-of > "static" variables. > > So I *can* check if the callback is called for the first time > but I *do not* know when it is called for the last time! > Knowing when I'm called for the first time allows me to build > the internal cache, and knowing when I'm called the last time > allows me to cleanup. This way the initialization and cleanup > are inherent for the callback procedure and nothing else is > needed from the outside to make it happen. > > But... > > After thinking more and more, I see that we can't simply > generalize that to be backward compatible. And if we can't > do that, then we'd had pretty inelegant solution. Therefore > I will step back and do as you suggested: before I register > the callback I will manually initialize it, and after I > unregister I will manually invoke the cleanup. > > I just though this can be somehow simplified but must admit > that this is not simple, given the code we already have. > > So, consider this idea trashed. Sorry for the noise... > > Cheers > Zoran > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |