{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"p5-Server-Starter-0.35p0","path":"net/p5-Server-Starter","url":"/packages/current/net/p5-Server-Starter/","comment":"superdaemon for hot-deploying server programs","homepage":"https://metacpan.org/release/Server-Starter","maintainer":"Abel Abraham Camarillo Ojeda <acamari@verlet.org>","description":"It is often a pain to write a server program that supports graceful\nrestarts, with no resource leaks. Server::Starter, solves the problem by\nsplitting the task into two. One is start_server, a script provided as a\npart of the module, which works as a superdaemon that binds to zero or\nmore TCP ports, and repeatedly spawns the server program that actually\nhandles the necessary tasks (for example, responding to incoming\ncommenctions). The spawned server programs under Server::Starter call\naccept(2) and handle the requests.\n","package_architecture":"*","stem":"p5-Server-Starter","readme":null,"dependencies":[{"path":"devel/p5-Module-Build","type":"build","package_spec":"","url":"/packages/current/devel/p5-Module-Build/"},{"path":"net/p5-Test-TCP","type":"test","package_spec":"STEM->=2.08","url":"/packages/current/net/p5-Test-TCP/"},{"path":"devel/p5-Test-Requires","type":"test","package_spec":"","url":"/packages/current/devel/p5-Test-Requires/"},{"path":"devel/p5-Test-SharedFork","type":"test","package_spec":"","url":"/packages/current/devel/p5-Test-SharedFork/"}],"reverse_dependencies":{"count":7,"url":"/packages/data/5c/5cbb607f40016d83cafba88b01593852567d1cf106ba4d92a08017def24cf71c.json"},"categories":["net","perl5"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}