I read through the docs on slinger.
I made a directory /web and put a single index.html file in it as a test.
I set my HTTPD_ROOT_DIR to /web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /web – Just as a test not as the final
resting place.
I set my permissions to rwxr-xr-x
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I ran pidin and verified all was running…
I slayed io-net and restarted in making sure the tiny stack was running –
just in case.
I started inetd and verified the two machines could talk tcp/ip using
telnetd.
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I cursed…
Are there other dependancies I need to know? (And if so – why not put them
in the docs?)
I don’t see anything in the docs saying there is something else I need to
do, what am I missing?
Pete Eddy
Hi Pete
I got slinger up and running pretty easily, though it fell way short of my
requirements.
First, I think you need the full stack (but I don’t know that).
What browser were you trying to use?
What did your URL look like?
Did you try?:
http://localhost/index.html
Can you ping localhost?
Until you get the local host version up and running I wouldn’t worry about
your two host version.
“Pete Eddy” <peter.w.eddy@lmco.com> wrote in message
news:a8vmgu$9h6$1@inn.qnx.com…
I read through the docs on slinger.
I made a directory /web and put a single index.html file in it as a test.
I set my HTTPD_ROOT_DIR to /web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /web – Just as a test not as the final
resting place.
I set my permissions to rwxr-xr-x
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I ran pidin and verified all was running…
I slayed io-net and restarted in making sure the tiny stack was running –
just in case.
I started inetd and verified the two machines could talk tcp/ip using
telnetd.
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I cursed…
Are there other dependancies I need to know? (And if so – why not put
them
in the docs?)
I don’t see anything in the docs saying there is something else I need to
do, what am I missing?
Pete Eddy
\
Pete
I set up slinger on a 4.25 and a 6.1 machine with no real difficulties, it
seemed to just work. I assume that you have got all your tcpip config files
set as you were able to telnet to the machine. I had mine set as localhost
and could use Voyager on the same machine without having the complication of
another computer. If you cannot see it with localhost I would start some
sysloging to try and isolate the problem.
The Docs example gives
I set my HTTPD_ROOT_DIR to /usr/web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /usr/web/cgi
also I set
CMD_INT=/bin/ksh
CONTENT_LENGTH=256
but this should not need to be done.
This might not be the problem but when trying something new I always follow
the docs verbatim until it works before trying something different.
Rod
“Pete Eddy” <peter.w.eddy@lmco.com> wrote in message
news:a8vmgu$9h6$1@inn.qnx.com…
I read through the docs on slinger.
I made a directory /web and put a single index.html file in it as a test.
I set my HTTPD_ROOT_DIR to /web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /web – Just as a test not as the final
resting place.
I set my permissions to rwxr-xr-x
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I ran pidin and verified all was running…
I slayed io-net and restarted in making sure the tiny stack was running –
just in case.
I started inetd and verified the two machines could talk tcp/ip using
telnetd.
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I cursed…
Are there other dependancies I need to know? (And if so – why not put
them
in the docs?)
I don’t see anything in the docs saying there is something else I need to
do, what am I missing?
Pete Eddy
\
The docs example said set the HTTPD variables and start slinger. I don’t
think I’m missing anything there. I have everybody in the hosts file, I
have the ip’s configured on each machine. Do I need to do something with
the services file to get port 80 to work?
It seem simple enough from looking at the docs.
Pete
“Rodney Stevens” <rodney.stevens@minerals.csiro.au> wrote in message
news:a8vqa5$btj$1@inn.qnx.com…
Pete
I set up slinger on a 4.25 and a 6.1 machine with no real difficulties, it
seemed to just work. I assume that you have got all your tcpip config
files
set as you were able to telnet to the machine. I had mine set as localhost
and could use Voyager on the same machine without having the complication
of
another computer. If you cannot see it with localhost I would start some
sysloging to try and isolate the problem.
The Docs example gives
I set my HTTPD_ROOT_DIR to /usr/web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /usr/web/cgi
also I set
CMD_INT=/bin/ksh
CONTENT_LENGTH=256
but this should not need to be done.
This might not be the problem but when trying something new I always
follow
the docs verbatim until it works before trying something different.
Rod
“Pete Eddy” <> peter.w.eddy@lmco.com> > wrote in message
news:a8vmgu$9h6$> 1@inn.qnx.com> …
I read through the docs on slinger.
I made a directory /web and put a single index.html file in it as a
test.
I set my HTTPD_ROOT_DIR to /web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /web – Just as a test not as the final
resting place.
I set my permissions to rwxr-xr-x
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I ran pidin and verified all was running…
I slayed io-net and restarted in making sure the tiny stack was
running –
just in case.
I started inetd and verified the two machines could talk tcp/ip using
telnetd.
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I cursed…
Are there other dependancies I need to know? (And if so – why not put
them
in the docs?)
I don’t see anything in the docs saying there is something else I need
to
do, what am I missing?
Pete Eddy
\
Yes I can ping localhost, and I try all variations of the
http://localhost/index.html I could thing of.
I also tried using the numeric addressing.
Pete Eddy
“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> wrote in message
news:a8vomf$b3h$1@inn.qnx.com…
Hi Pete
I got slinger up and running pretty easily, though it fell way short of my
requirements.
First, I think you need the full stack (but I don’t know that).
What browser were you trying to use?
What did your URL look like?
Did you try?:
http://localhost/index.html
Can you ping localhost?
Until you get the local host version up and running I wouldn’t worry about
your two host version.
“Pete Eddy” <> peter.w.eddy@lmco.com> > wrote in message
news:a8vmgu$9h6$> 1@inn.qnx.com> …
I read through the docs on slinger.
I made a directory /web and put a single index.html file in it as a
test.
I set my HTTPD_ROOT_DIR to /web
I set my HTTPD_ROOT_DOC to index.html
I set my HTTPD_SCRIPTALIAS to /web – Just as a test not as the final
resting place.
I set my permissions to rwxr-xr-x
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I ran pidin and verified all was running…
I slayed io-net and restarted in making sure the tiny stack was
running –
just in case.
I started inetd and verified the two machines could talk tcp/ip using
telnetd.
I ran slinger.
I tried connecting from two node configuration, no dice…
I tried connecting to localhost, no dice…
I cursed…
Are there other dependancies I need to know? (And if so – why not put
them
in the docs?)
I don’t see anything in the docs saying there is something else I need
to
do, what am I missing?
Pete Eddy
\
Pete
I will try and remember if I had to do anything else, but I think it just
worked for me sorry I cannot be of much further help. What I was alluding to
was the PATH /usr/web, that was all.
Rod
After I sent out that last Email, I check my /etc/services file. No port 80
defined…
hmmm, I thought…
So I added added http on port 80, tried the webstart script I had written,
and started
voyager. Viola! My test page came up.
So, to answer my own question for anybody reading this YES you do need to
change the
/etc/services file, or at least make sure it has a line for http on port 80.
After I got slinger to work I started playing around with the SSI routines.
I got the to work, I think I like that better
than cgi without SSI.
What are the limitations of slinger? It seems pretty decent, off hand, but
I’m not real familar
with web servers. I wan’t to serve up some documentation, and maybe query a
documentation
control system. You know just basic stuff.
Pete Eddy
“Rodney Stevens” <rodney.stevens@minerals.csiro.au> wrote in message
news:a92kff$fr7$1@inn.qnx.com…
Pete
I will try and remember if I had to do anything else, but I think it just
worked for me sorry I cannot be of much further help. What I was alluding
to
was the PATH /usr/web, that was all.
Rod
Pete
Good to hear you got it going, I must admit that I didn’t have to touch the
/etc/services file on either of my implementations of slinger.
I have done both SSI and CGI programming with slinger. Forms with javascript
work, but that is about as far as I have gone. We have dynamic update of
one of our pages, but nothing special just redraw the page every 10 secs.
It was fun, good luck.
Rod