Having to use % as a wildcard isn't intuitive to the average user, and even with an explanation right on the
search page I don't think they would use it.
On Krzysztof's page I was able to use * as a wildcard to make "PalmPilot" a hit
on a search for "*pilot", but I guess it's not one bit more intuitive😊
I'd like to run swish++ as a daemon and I got the "non-daemon" search running.
Why can't I load nsunix witch I presume is needed? All permissions look right to me.
This is what the log file says:
[30/Aug/2000:17:15:59][4955.1024][-main-] Error: nsunix: could not listen: File or directory doesn't exist.
[30/Aug/2000:17:15:59][4955.1024][-main-] Notice: binder: listen(127.0.0.1, 80) = 17
[30/Aug/2000:17:15:59][4955.4101][-nssock-] Notice: waiting for startup
[30/Aug/2000:17:16:00][4955.1024][-main-] Notice: AOLserver/3.0 running.s
A snippet from my nsd.tcl:
ns_section "ns/server/${server}/module/swish-search"
ns_param PathToSearch "/tmp/swish++-4.6.6/search"
ns_param PathToIndex "${pageroot}/history/swish++.index
ns_param UseDaemon 1
ns_param SocketName "/tmp/search.socket"
# Unix domain socket driver -- nsunix
#
ns_section "ns/server/${server}/module/nsunix"
ns_param hostname $hostname ;# Hostname used in response to client
ns_param port 80 ;# Port to listen on
ns_param socketfile "/tmp/search.socket" ;# UNIX domain socket driver
ns_section "ns/server/${server}/modules"
ns_param nssock ${bindir}/nssock.so
ns_param nslog ${bindir}/nslog.so
ns_param nsperm ${bindir}/nsperm.so
ns_param nscp ${bindir}/nscp.so
ns_param nsunix ${bindir}/nsunix.so
