>> I am setting this up atm. I will try to put together a readme we can include
>> for nginx / httpd configurations.
>
> Before/while you are at it:
>
> Kristaps: Slant doesnt't appear to support specifying port number in the
> URL in .slantrc, like:
>
> $ tail -n 3 ~/.slantrc
> servers
> http://192.168.1.1:81/cgi-bin/slant-cgi
> ;
>
This is now fixed. It now accepts port numbers and HTTP authentication
u/p in case you want private server data. I've enclosed the newest
version 0.0.13, which also has some additional fixes since the initial
submission. Namely, HTTP/1.1 server recognition and some timeout stuff.
I also specify that the newest kwebapp must be there---I sent this as an
update to the list.
None of the updates affect the collector or CGI script---just the client.
> $ tail -n 2 ~/.slant-errlog
> DNS resolving: 192.168.1.1:81
> Warning: DNS parse error: 192.168.1.1:81: no address associated with name
>
> I was about to attempt some tinkering in dns_parse_url in slant-dns.c
> but gave up since I could not for the life of me get the sources from
> your website to compile:
>
> ---8<---
> $ make
> kwebapp-sql slant.kwbp > slant.sql
> rm -f slant.db
> sqlite3 slant.db < slant.sql
> kwebapp-c-header -s -g EXTERN_H -Nd slant.kwbp > extern.h
> kwebapp-c-header -s -Nb slant.kwbp > db.h
> cc -O2 -pipe -g -W -Wall -Wextra -Wmissing-prototypes -Wstrict-prototypes -Wwrite-strings -Wno-unused-parameter -DVERSION=\"0.0.10\" -c slant-collectd.c
> cc -O2 -pipe -g -W -Wall -Wextra -Wmissing-prototypes -Wstrict-prototypes -Wwrite-strings -Wno-unused-parameter -DVERSION=\"0.0.10\" -c slant-collectd-openbsd.c
> kwebapp-c-source -s -h extern.h,db.h slant.kwbp > db.c
> cc -O2 -pipe -g -W -Wall -Wextra -Wmissing-prototypes -Wstrict-prototypes -Wwrite-strings -Wno-unused-parameter -DVERSION=\"0.0.10\" -c db.c
> cc -o slant-collectd slant-collectd.o db.o slant-collectd-openbsd.o -lksql -lsqlite3
Looks like it's compiling just fine.
It depends upon kwebapp, which is generating the following from slant.kwbp:
- object API (extern.h)
- database<->object API (db.h, db.c)
- JSON<->object input and output (json.c, json.h)
It then builds the collector, which uses the database input/output bits;
the CGI script, which uses the database and JSON bits; and the client,
which uses the JSON bits.
> Otherwise I love the little rascal, running it on seven machines so far,
> but think the need for allowing to specify alternate ports will show up
> from other users soon enough.
Thanks for the input!
No comments:
Post a Comment