Thanks guys, I am running Apache 2.4.10.
Good idea Harald, I did not think about it. I will check and report. Thanks. This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/sig-email> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Feb 12, 2016 at 10:36 AM, Massimo Manghi <[email protected]> wrote: > What version of Apache are you running? > > -- M > > > > On 12-02-2016 16:25, Brice Hamon wrote: > >> Hi guys, >> >> I re-install the host from scratch with Opensuse 13.2. >> >> I recompiled Rivet with the basic options: --with-aspx=/usr/bin/aspx2 >> --prefix=/usr/local >> >> The configure output is: >> >> checking for tclsh... /usr/bin/tclsh8.6 >> configure: we are building Rivet with Tcl 8.6.3 >> checking mod_rivet core... apache-2 >> checking for Apache base... /usr/local/apache2 >> checking for Apache apxs... /usr/bin/apxs2 >> checking for Apache apr... checking for apr-1-config... >> /usr/bin/apr-1-config >> /usr/bin/apr-1-config >> checking for Apache apu... 1.5.3 >> apu-1-config >> checking for Rivet tcl library target... >> /usr/local/apache2/lib/rivet2.2.4 >> checking whether rivet version is printed in Apache signature... no, >> Rivet version will be hidden >> checking where Rivet will save uploads... /tmp >> checking whether Rivet has to honor HEAD requests... no, Rivet will >> shunt HEAD requests >> checking whether Rivet will create an interpreter for each virtual >> host... no >> checking maximum size of a POST... unlimited size >> checking whether files are uploaded to Tcl variables... yes >> checking if ::rivet namespace will be automatically imported for >> compatibility... yes >> checking code for request handling... request >> checking for Rivet core commands code... rivetcmds >> checking for Rivet channel code path... channel >> checking Major version... 2 >> checking Minor version... 2 >> checking Point version... 4 >> configure: Rivet package version is 2.2 >> configure: forcing Rivet to export commands from ::rivet namespace >> >> Rivet works great, pages are generated normally. But I cant create a >> log file or write an upload files into the local file system. >> The web server forked https as wwwrun as usual. There is nothing I can >> think of preventing the interpreter to write to the local file system >> accroding to the user rights. >> >> Any hints? >> >> Thank you. >> Brice. >> >> > >
