Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Alexey Pechnikov
Hello! On Sunday 01 March 2009 04:37:44 Don Baccus wrote: nspostgres works fine with both aolserver 4.0.10 and 4.5.  It's used   in production at education sites with tens of thousands of users   running aolserver/postgres-based e-learning software. AOL Server 4.5 doesn't work with PostgreSQL

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Alexey Pechnikov
Hello! On Saturday 28 February 2009 21:35:21 Tom Jackson wrote: There is an nsdb module nssqlite3. Here is the readme: http://junom.com/gitweb/gitweb.perl?p=aolserver.git;a=blob;f=nssqlite3/READ ME;hb=HEAD There are a lot of modules in the repository but some ot these are old and may be

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Tom Jackson
On Sun, 2009-03-01 at 13:02 +0300, Alexey Pechnikov wrote: Hello! On Sunday 01 March 2009 04:37:44 Don Baccus wrote: nspostgres works fine with both aolserver 4.0.10 and 4.5. It's used in production at education sites with tens of thousands of users running aolserver/postgres-based

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Tom Jackson
On Sun, 2009-03-01 at 14:06 +0300, Alexey Pechnikov wrote: Hello! On Saturday 28 February 2009 21:35:21 Tom Jackson wrote: There is an nsdb module nssqlite3. Here is the readme: http://junom.com/gitweb/gitweb.perl?p=aolserver.git;a=blob;f=nssqlite3/README There are a lot of modules in

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Alexey Pechnikov
Hello! On Sunday 01 March 2009 04:37:44 Don Baccus wrote: nspostgres works fine with both aolserver 4.0.10 and 4.5.  It's used   in production at education sites with tens of thousands of users   running aolserver/postgres-based e-learning software. Please see

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Don Baccus
On Mar 1, 2009, at 9:21 AM, Tom Jackson wrote: On your datatype problem below, what is the problem? Why would you care about such a failure? And why not ask on a postgreSQL list, or a debian list when you have problems with their software? Tom ... chill. He just mentioned a datatype

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Don Baccus
On Mar 1, 2009, at 9:45 AM, Alexey Pechnikov wrote: nspostgres doesn't work as you can see Huh. Tell that to those of us using it w/o problems. Don Baccus http://donb.photo.net http://birdnotes.net http://openacs.org -- AOLserver - http://www.aolserver.com/ To Remove yourself from

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Don Baccus
On Mar 1, 2009, at 9:45 AM, Alexey Pechnikov wrote: http://www.google.com/search?hl=enq=nspostgres+received+fatal +signal+11btnG=Search nspostgres doesn't work as you can see. I know for a fact that Iuri, the last person who shows up for that search, got it working and in fact has used

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Dossy Shiobara
On 3/1/09 6:06 AM, Alexey Pechnikov wrote: There are a lot of modules in the repository but some ot these are old and may be not-supported. Are these tested with AOL 4.0/4.5/4.6? I suspect that individual sites are using and testing various configurations, but there's no official QA team for

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Alexey Pechnikov
Hello! On Sunday 01 March 2009 21:05:30 Don Baccus wrote: http://www.google.com/search?hl=enq=nspostgres+received+fatal +signal+11btnG=Search nspostgres doesn't work as you can see. I know for a fact that Iuri, the last person who shows up for that   search, got it working and in fact

[AOLSERVER] Load module for all connections

2009-03-01 Thread Alexey Pechnikov
Hello! I did try to create sqlite connection for all threads by creating test.tcl in tcl library directory. But it isn't work. $ cat test.tcl package require sqlite3 sqlite3 ::dbtest :memory: By using adp pages or control port command puts [dbtest onecolumn {select 1}] doesn't work. Is this

[AOLSERVER] Exec error produce error Fatal: received fatal signal 11.

2009-03-01 Thread Alexey Pechnikov
Hello! AOL version 4.5 may be killed my simple code: catch {exec soffice -invisible -headless -norestore macro:///Standard.Converter.ConvertToPDF($tmpdocname) -display :10} I rewrite command as exec soffice -invisible -headless -norestore macro:///Standard.Converter.ConvertToPDF($tmpdocname)

Re: [AOLSERVER] Exec error produce error Fatal: received fatal signal 11.

2009-03-01 Thread Dossy Shiobara
On 3/1/09 4:45 PM, Alexey Pechnikov wrote: catch {exec soffice -invisible -headless -norestore macro:///Standard.Converter.ConvertToPDF($tmpdocname) -display :10} I rewrite command as exec soffice -invisible -headless -norestore macro:///Standard.Converter.ConvertToPDF($tmpdocname) -display :10

Re: [AOLSERVER] Exec error produce error Fatal: received fatal signal 11.

2009-03-01 Thread Bas Scheffers
On Monday, March 2, 2009 8:15am, Alexey Pechnikov pechni...@mobigroup.ru said: I rewrite command as ... It's work but is not stable. Using exec is generally unstable, not sure why, but it is certainly not recommended. I would try some other way, like ns_proxy.

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Gustaf Neumann
Alexey, don't use binaries of drivers compiled for 4.0.* with 4.5.* and vice versa; this can easily lead to crashes. Make as well sure, that all involved binaries are compiled against the same version of tcl. nspostgres does work with 4.0.10 and 4.5.0 and 4.5.1 with all recent versions of

Re: [AOLSERVER] Exec error produce error Fatal: received fatal signal 11.

2009-03-01 Thread Gustaf Neumann
dear alexey, Strange, both commands behave as expected on my machine with aolserver 4.5.1. Can it be that your machine is running out of memory? Can it be that you have mixed tcl versions during compilation? btw, you should use nsproxy instead of exec to call soffice. best regards -gustaf

Re: [AOLSERVER] AOL + SQLite+nsproxy question

2009-03-01 Thread Alexey Pechnikov
Hello! On Monday 02 March 2009 01:24:08 Gustaf Neumann wrote: don't use binaries of drivers compiled for 4.0.* with  4.5.* and vice versa; this can easily lead to crashes. Make as well sure, that all involved binaries are compiled against the same version of tcl. nspostgres does work with