[systemd-devel] 'tasks' as first-order objects?

[Tollef Fog Heen]

]] Lennart Poettering 

| > > So, maybe "Type=transient" is nicer? Sounds a bit scientific but this
| > > word is not unheard in the Free software world at least (i.e. X uses
| > > that iirc) and describes pretty accurately what these kind of processes
| > > are used for, i.e. transient, temporary, short-running processes? Other
| > > suggestions?
| > 
| > 'function'
| > 'oneshot'
| > 'single'
| > 'not-respawning'
| > 
| > (None of these are necessarily good.)
| 
| "oneshot" sounds the best choice from this list to me. What are your
| opinions on "transient"?
| 
| I am tempted to do s/finish/transient/. Anybody else has an opinion on
| this?

I'd be happier with Type=oneshot, since it communicates more clearly
what it is about, especially to people without a math/CS background.

| Example: on suse early boot scripts also carry LSB information and can
| be started in parallel. Some of them are more service-like (e.g. the
| one that runs spawns udev very early on bootup) and others more
| tasks-like (e.g. fsck). And we couldn't figure out just by prsing the
| LSB headers what type this is. On Fedora we have a couple of services
| like this, too, such es iptables.

Debian is like suse here as well, fwiw.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are