Q. Do you have any plans to support the other
A. Patches are gladly accepted, although I can't make
any guarantees of quality or testing on my end. I really
don't have much time to work on this, so my work will
tend to be sporadic but intensive, and fundamentally
based on what i need to get done for my employer. But
others can certainly help if they'd like to.
Q. Why do you use getcap(3) configuration
A. It's included in the base distribution, so there
are no extra libraries needed. Also, I'm lazy and
don't want to mess with YACC.
I've tried to keep everything as plain-vanilla as
isn't hard to learn, but it is just a little picky
Q. getcap(3) won't let me use colons in my expect strings or URLs. Is there any way around this?
A. YES! getcap(3) uses escape sequences to express prohibited characters. See the man page for more information. Just for kicks, the escape sequence for a colon is "\c" (obviously without the double-quotes).
Q. This seems like it's mostly geared toward web servers. Why is that?
A. Because it is. That's what we use load balancers for,
so that's the major focus now. Maybe eventually we'll do more fun stuff.
Q. It doesn't work for me. What now?
A. I don't know what to tell you. Look at your syslog
messages to see if it is trying to tell you something.
You can email me if you want or post on the
SourceForge message boards, but don't hold your
breath. Remember, this is BSD-licensed software and
implies no guarantee or warranty.
Q. OpenBSD sucks/OS <whatever> is better!
A. Then don't use OpenBSD.
Thanks go to...
my employer, Silas Partners, for allowing me to release the code for the project
The current maintainer can be reached at the address below. Just replace "spamfree.net" with "users.sourceforge.net". firstname.lastname@example.org
The author can be reached at the address below. Just replace "spamfree.net" with "users.sourceforge.net". email@example.com