Support running from a socket again in sassserver

 A sassserver can run the same when forked or spawned from a
local service, that's the point of textclient. Most sassservers
don't need local service support in any way, and cutting the
support from that saves pulling a good amount of code, but some
do. Put back local service support while refactoring the code
so running as a child from the client (common case) doesn't pull
the socket code.

1 files changed, 13 insertions, 0 deletions

diff --git a/src/libunixonacid/sassserver_init_fromsocket.c b/src/libunixonacid/sassserver_init_fromsocket.c
new file mode 100644
index 0000000..48fd1d4
--- /dev/null
+++ b/src/libunixonacid/sassserver_init_fromsocket.c
@@ -0,0 +1,13 @@
+/* ISC license. */
+
+#include <skalibs/strerr.h>
+#include <skalibs/textclient.h>
+#include <skalibs/sassserver.h>
+#include "sassserver-internal.h"
+
+void sassserver_init_fromsocket (sassserver *a, char const *banner1, char const *banner2, sassserver_send_func_ref sendf, sassserver_cancel_func_ref cancelf, size_t datasize, free_func_ref cleanupf, void *aux, tain const *deadline, tain *stamp)
+{
+  if (!textclient_server_01x_init_fromsocket(banner1, strlen(banner1), banner2, strlen(banner2), deadline, stamp))
+    strerr_diefu1sys(111, "sync with client") ;
+  sassserver_init_structures(a, sendf, cancelf, datasize, cleanupf, aux) ;
+}