Re: hoststated - some questions

2007-12-06 Thread Pierre-Yves Ritschard
[sent to wrong list]

 Also hoststatectl reload does not work for me.
 
 [EMAIL PROTECTED] root# hoststatectl reload
 command failed
 
 Expected behavior?
 

Unfortunately, yes.
reload currently does not work for layer7 (relay) configurations.
it should be available before 4.3 though.



hoststated - some questions

2007-12-05 Thread Chad M Stewart
I am working with hoststated and trying to figure out if it will work  
for what I want to do.   I have some questions that I hope people can  
answer for me.


kern.version=OpenBSD 4.2-stable (GENERIC) #0: Sun Dec  2 13:43:16 GMT  
2007

[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC


- where does it log?  Even running with -dvv I don't see output that  
I am expecting, which could simply be I'm expecting the wrong thing.   
For example


# from configuration file
protocol httpcustom {
protocol http
 header append $REMOTE_ADDR to X-Forwarded-For log
 header append $SERVER_ADDR:$SERVER_PORT to X- 
Forwarded-By log

tcp { nodelay, sack, socket buffer 65536, backlog 128 }
}


Results in the following output when run with -dvv

protocol 0: name httpcustom
flags: 0x0004
type: http
request append $SERVER_ADDR:$SERVER_PORT to X- 
Forwarded-By

request append $REMOTE_ADDR to X-Forwarded-For


Note the log action is gone.  When I hit the service with a browser  
and watch the tcpdump on the web server, the headers are added,  
great.  But I don't see any evidence of it from hoststated.   I'm  
trying to see if/how I would have hoststated go about looking at the  
Host: header in HTTP.   Figured I'd start with the example and work  
from there.  I'm wondering if hoststated can replace squid in front  
of a couple of name based virtual http servers, thus the need to get  
at the host header to find/lookup the destination.



Also hoststatectl reload does not work for me.

[EMAIL PROTECTED] root# hoststatectl reload
command failed

Expected behavior?




Thank you,
Chad