I have Ubuntu Studio on which Debian "dwww" is installed. I needed to fix some directories by adding symbolic links to get everything to work. But for now, if I click on a command to see its manpage or documentation, I am asked to download the gzipped file. It is not uncompressing and converting to html. I imagine it should do something if it is appending ?type=man to all of the links. But I don't see a script to run the CGI query. There are none in the dwww directory, nor under dwww/cgi-bin (to non-Debian users, that's http://hostname/dwww). There was never a cgi-bin directory at any rate. I actually had to create one so the links to the manpages wouldn't break, but there are no scripts in there unless I wrote it, and I didn't write any. What is this script supposed to be called? There are no clues in the HTML. Can I download it from somewhere? pkingman
Hi Paul -
… But for now, if I click on a command to see its manpage or documentation, I am asked to download the gzipped file.
This sounds like a very old bug I experienced years ago where dwww-convert didn't know about gzipped files. Is there anything to this effect in your /etc/dwww/dwww.conf? Is dwww-index++ being run periodically? You might be hitting permission problems between the new symlinked man page directories and where apache2 and dwww is allowed to look. cheers, Stewart
On 2016-02-21 15:48, Stewart C. Russell wrote:
Hi Paul -
… But for now, if I click on a command to see its manpage or documentation, I am asked to download the gzipped file.
This sounds like a very old bug I experienced years ago where dwww-convert didn't know about gzipped files. Is there anything to this effect in your /etc/dwww/dwww.conf? Is dwww-index++ being run periodically?
That's the problem with my configuration. There is just index.html, dwww.css, and the PNG of the Debian logo. No hidden files either. There was nothing under ../cgi-bin, since it wasn't there until I created it. Thus, there is no dwww.conf, and dwww-index++ (is that the name of a script?) is nowhere in sight. There is also no cgi code inside the index.html telling me what the script thinks should be handling the ?type=man at the end of the URL.
You might be hitting permission problems between the new symlinked man page directories and where apache2 and dwww is allowed to look.
Or I could be just going up against an ill-equipped documentation system, stripped down by Ubuntu. :-(
cheers, Stewart
Regards Paul
What finally worked came from an ubuntu forum dated some time last year: 1. send this command to apache: sudo a2enmod cgi My server responded with a warning, but then ended with Enabling module cgi. 2. Restart apache sudo service apache2 restart Once again, I got a warning, but the web browser began to do the right thing. In fact, those directories and symbolic links I made earlier were for nothing. It doesn't need /cgi-bin, even though it's in the URL, for example. It also doesn't appear to need a link to /usr, since it looks like there's a more secure way to access the manpages also. Thanks, Stewart for your help Paul
participants (2)
-
sciguy -
Stewart C. Russell