Re: [fossil-users] Using althttpd.c

2011-11-10 Thread Konstantin Khomoutov
On Thu, Nov 10, 2011 at 10:57:37PM +0100, Paolo Bolzoni wrote:

> Today I tried to use althttpd.c as HTTP server for serving few fossil
> scm. But I cannot execute CGI scripts.
[...]
> Now once I start xinetd if I go to 127.0.0.1 with my browser
> the server greets me saying there is no document in / that is fine.
[...]

Is there any reason not to run fossil directly from inetd to serve a
directory with repositories?  Fossil is really self-hosting and does not
need a HTTP server because it's itself a HTTP server.

For instance, I have:

~% grep fossil /etc/inetd.conf   
8080 stream tcp nowait fossil /usr/local/bin/fossil /usr/local/bin/fossil http 
/var/local/lib/fossil/

That /var/local/lib/fossil/ directory contains a set of *.fossil files.
This allows me to use http://that_host:8080/repo/ to acces the
"repo.fossil" repository.  This works for both kinds of access: using
fossil client for pushes/pulls and using a browser for interactive
stuff.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Using althttpd.c

2011-11-10 Thread Dmitry Chestnykh
Hello,

On Thu, 10 Nov 2011 22:57:37 +0100 Paolo Bolzoni 
wrote:

> I thought if could be a problem with the root jail but
> even if I copy sh in the default.website directory and change
> the interpreter to #!/sh nothing changes.

Are you sure that 'sh' doesn't depend on anything else and is
statically linked?

Try with statically linked fossil:

./configure --static
make

-- 
Dmitry Chestnykh
http://www.codingrobots.com
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Using althttpd.c

2011-11-10 Thread Paolo Bolzoni


Today I tried to use althttpd.c as HTTP server for serving few fossil
scm. But I cannot execute CGI scripts.

The althttpd.c file I am speaking of is this one:
http://www.sqlite.org/docsrc/artifact/14c9965da19e83baeba2cd81b6459f3948f73794

So I downloaded it, compiled it, copied in /usr/local/bin/httpd .

My distribution uses xinetd so I made a configuration file to start httpd.

Here is the configuration file content:

service http
{
    socket_type = stream
    protocol = tcp
    port = 80
    wait = no
    user = root
    group = root
    server = /usr/bin/httpd
    server_args = -logfile logfile -root /home/paolo/tmp -user nobody
}

I set the root directory as /home/paolo/tmp just as test.

Inside the directory /home/paolo/tmp/default.website are two files:

a.txt a text file
b.sh a script with this content:

-
#!/bin/sh
echo A
-

Now once I start xinetd if I go to 127.0.0.1 with my browser
the server greets me saying there is no document in / that is fine.

Also 127.0.0.1/a.txt works fine, but if I try 127.0.0.1/b.sh the page
loads for some seconds and it shows an empty page.

What I am doing wrong? Why the CGI does not work?

I thought if could be a problem with the root jail but
even if I copy sh in the default.website directory and change
the interpreter to #!/sh nothing changes.

Help please.
Thanks
  
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Internal Server Error on files page after push

2011-11-10 Thread Richard Boehme
Thanks for the quick reply. I'll check on that when I get back tonight.

Richard


On Thu, Nov 10, 2011 at 9:13 AM, Richard Hipp  wrote:
>
>
> On Thu, Nov 10, 2011 at 9:07 AM, Richard Boehme  wrote:
>>
>> Any thoughts on why fossil push would end up with my server's files
>> page giving me an internal server error?
>
>
> The repository file, the directory that contains the repository file and
> /tmp all need to be readable and writable by whatever user CGI is running
> under.
>
> --
> D. Richard Hipp
> d...@sqlite.org
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>



-- 
Thank you.

Richard Boehme

Email: rboe...@gmail.com
Phone: 443-739-8502
Blog: http://www.inexperiencetalking.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Internal Server Error on files page after push

2011-11-10 Thread Richard Hipp
On Thu, Nov 10, 2011 at 9:07 AM, Richard Boehme  wrote:

>
> Any thoughts on why fossil push would end up with my server's files
> page giving me an internal server error?
>


The repository file, the directory that contains the repository file and
/tmp all need to be readable and writable by whatever user CGI is running
under.

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Internal Server Error on files page after push

2011-11-10 Thread Richard Boehme
Hi there. I'm having a bit of trouble with fossil push. I have one
local machine (Win 7) that I originally created the fossil repository
on (just a blank repository). I copied it to my linux server and ran
it with Apache over CGI. I also made sure that the same version of
fossil was on my local machine and the server. At this time, the
project's "files" page showed no files (as expected). I added files
with fossil add and fossil commit (and could see the files in the
local fossil instance), and then tried to push to the server's URL.
The client complained that it didn't have permission to write to the
local fossil executable (no permission for xapps/bin/fossil.exe - I
don't know where it got the "x" in there). When I looked into the
server's fossil repository, I could get into the repository itself,
but the "files" tab gave me an internal server error.

My initial fossil commit on my local machine asked about crlf style,
but the local repository files look file. It's only the server file
page that is screwed up. I tried doing a fossil rebuild on the server
- that didn't help; neither did creating another repository from
scratch on the server.

Any thoughts on why fossil push would end up with my server's files
page giving me an internal server error? If needed, I can get exact
wording once I'm back in range of my computers at home.

-- 
Thank you.

Richard Boehme

Email: rboe...@gmail.com
Phone: 443-739-8502
Blog: http://www.inexperiencetalking.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users