Scrum Daemon Design Document

[mkohlmyr]

• The scrum daemon is a net server listening on the /tmp/scrumd.sock unix socket.
• The scrum daemon maintains a map s.t.

{
    [ppid]: {
        session: [session slug],
        children: {
            [pid]: {
                window: [window slug]
                command: [ps-aux command column]
            }
        }
    }
}

• When the scrum command is ran we attempt to connect to the unix socket, and if it fails we spawn the daemon in the background.
• When the scrum daemon exits or hits an exception, it should remove the unix socket file.
• The scrum daemon is queried by scrum status, scrum status session and scrum status session window and sent data by scrum start. Each of these will trigger the daemon to look up process information for all processes under the available ppids, and update the process map.
• scrum status and related commands should all receive the full map back from the daemon (brings us down to a minimal daemon). They can then scale that data down to what was actually asked for.
• Data returned from daemon to scrum status and related should print as what is essentially a process tree, not unlike ps -ejH. The scrum command will extract and print what was asked for.