<feed xmlns='http://www.w3.org/2005/Atom'>
<title>skalibs/src/libunixonacid/sassserver_init_frompipe.c, branch main</title>
<subtitle>The skarnet.org C programming library</subtitle>
<id>https://git.skarnet.org/cgit/skalibs/atom/src/libunixonacid/sassserver_init_frompipe.c?h=main</id>
<link rel='self' href='https://git.skarnet.org/cgit/skalibs/atom/src/libunixonacid/sassserver_init_frompipe.c?h=main'/>
<link rel='alternate' type='text/html' href='https://git.skarnet.org/cgit/skalibs/'/>
<updated>2026-04-07T14:28:10Z</updated>
<entry>
<title> Support running from a socket again in sassserver</title>
<updated>2026-04-07T14:28:10Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2026-04-07T14:28:10Z</published>
<link rel='alternate' type='text/html' href='https://git.skarnet.org/cgit/skalibs/commit/?id=b8afece8d141369c25027b73680deccf48ddb948'/>
<id>urn:sha1:b8afece8d141369c25027b73680deccf48ddb948</id>
<content type='text'>
 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.
</content>
</entry>
</feed>
