COME FROM
COME FROM
Posted Feb 11, 2014 12:46 UTC (Tue) by cesarb (subscriber, #6266)Parent article: Systemd programming part 2: activation and language issues
> There is a key difference here, though, and it isn't really about events or dependencies, but about causality. In upstart, a job can declare "start on" to identify which event it should start on. So each job declares the events which cause it to run. Systemd, despite its rich dependency language, has no equivalent to "start on", an omission that appears to be deliberate. Instead, each event — the starting or stopping of a unit — declares which jobs (or units) need to be running. The dependency language is exactly reversed. With upstart, each job knows what causes it to start. With systemd, each job knows what it causes to start.
Let's see if I understood this correctly. Upstart's behavior is like COME FROM, while systemd's is more like GO TO.
