ccheney seems to have the right idea here. approx no longer runs as its
own service; it runs through inetd, which means that it expects stdin
and stdout to be a socket, not normal fds (hence why it doesn't work
when you launch it manually)
Please check /etc/inetd.conf for the approx configuration, and restart
openbsd-inetd to make sure that it's picked up the configuration.
** Changed in: approx (Ubuntu)
Status: New => Incomplete
--
approx doesn't work in Karmic/Lucid
https://bugs.launchpad.net/bugs/517474
You received this bug notification because you are a member of Debian
OCaml Maintainers, which is subscribed to approx in ubuntu.
Status in “approx” package in Ubuntu: Incomplete
Bug description:
Binary package hint: approx
Just upgraded a working approx server from Jaunty to Karmic.
1) There's no approx service anymore in init.d. No way to launch approx as a
service
2) By trying to launch approx manually, you got :
getsockname: Socket operation on non-socket
_______________________________________________
Mailing list: https://launchpad.net/~ocaml-maint
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ocaml-maint
More help : https://help.launchpad.net/ListHelp
