https://github.com/eylles/shed

init independient user services and graceful gui session log out
https://github.com/eylles/shed

0ver daemon linux posix-sh posix-shell session-management shell shell-script user-services

Last synced: about 2 months ago
JSON representation

init independient user services and graceful gui session log out

• Host: GitHub
• URL: https://github.com/eylles/shed
• Owner: eylles
• License: gpl-3.0
• Created: 2022-08-10T15:49:26.000Z (over 2 years ago)
• Default Branch: master
• Last Pushed: 2024-11-01T22:17:12.000Z (2 months ago)
• Last Synced: 2024-11-01T23:19:20.763Z (2 months ago)
• Topics: 0ver, daemon, linux, posix-sh, posix-shell, session-management, shell, shell-script, user-services
• Language: Shell
• Homepage:
• Size: 133 KB
• Stars: 7
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# SHED

An init and service manager for user services























## what?

Session services, programs that run as part of your graphical session, for example in x11 you have the compositor, keyring, maybe a clipboard daemon and perhaps pulseaudio or pipewire

## dependencies

- a posix compatible shell interpreter

- core unix utilities (date, mkdir, awk, kill, mkfifo, cat)

- ~~inotifywait from the inotify-tools package (i know freebsd got the program but not what to use in other unices)~~ no longer needed, now a named pipe is used.

## why ?

Some programs have the tendency to missbehave when started in a session process in non systemd distros, the prime example right now being pipewire which has spawned this [pipewire #1099](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1099) and this [pipewire #1135](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1135) as the issue comments say, this problem forced gentoo to write a wrapper and slackware to roll out a custom [daemon](https://github.com/raforg/daemon) program written in C, in my opinion both of these solutions are less than ideal, on gentoo's case they now have to roll out similar wrappers for other missbehaving programs, the slackware program looks unnecessarily overengineered as it still needs more programs to be started correctly.

And the elephant in the room, both these solutions come out as inferior to the likes of systemd units and runit user services as they don't support restarting for reloading configurations nor a correct way for them to be started and stopped by the user.

That is why i came up with this solution that takes a lot of inspiration from the sysvinit architecture with the aim of keeping simple, intuitive and completely agnostic from any window manager and desktop environment, potentially even agnostic to any graphical environment (altho i personally only care or x11)

TODO:

- [ ] rewrite readme

- [x] move the details of how shed works to another .md file

- [x] add check if the service is running in start, kill and hup

- [x] add service status action to shedc

- [x] add service restart action to shedc

- [x] add a shed daemon reply socket, so that shedc can wait that shed is reloaded.

- [x] make shedc tail and read the reply socket

- [ ] write bash completion scripts

- [ ] write zsh completion scripts

- [ ] draw a logo/icon for shed to use in the repo

## DO NOT USE THE GIT MASTER EVER!

The git master is unstable and may break without notice, always use shed from a release tag.