[02:28] Keybuk: ping === Md_ is now known as Md [12:26] sadmac: pong [16:57] Keybuk: I was wanting to ask about your current thoughts for the profiles system [17:44] sadmac: sure [17:51] Keybuk: What does your design for it look lik? [17:51] I don't have one [17:51] s/lik/\0e/ [17:51] AlexExtreme has been doing one, iirc [17:51] the idea being to define profiles in a file [17:51] that look something like [17:51] disable apache [17:51] disable squid [17:51] or [17:51] disable * [17:51] enable foo [17:51] enable bar [17:52] hmm [17:52] I had another idea for it [17:53] my idea was to add a stanza to the job definitions, one of either "disable unless" or "disable if" [17:53] followed by a series of flag names. [17:53] we could then load a list of set flags off the filesystem at boot time. [17:59] that does get kind of messy if you have flags with large effects, like single user mode. [18:08] yeah, that's more in line with the "flags" idea [18:09] flags and profiles are two competing ideas for the same functionality [18:09] profiles implies that profile is a first-class object which includes or excludes jobs [18:09] and maybe that you only have one profile active at one time [18:09] flags is that jobs disable/enable themselves in their own configuration depending on which flags are set [18:09] with the implication that multiple flags can be set at one time [18:10] the profiles idea is better for a sysadmin, since they don't need to edit the job definitions [18:10] flags is vaguely better for a distro [18:22] Keybuk: with enough flags built into the jobs they become logically equivalent [18:23] that's somewhat true [18:23] one of the other inits has a feature whereby kernel arguments turn on/off jobs [18:24] thats easy to do. Doesn't even have to be done in code. [18:25] an early job definition that takes a peak at /proc could do it. [19:59] does upstart work if it's not PID 1? [19:59] as the child of another init? [20:00] no [20:01] aw. how come? :) [20:03] you can run it as another pid by disabling a couple of its features [20:03] (supervision of forking daemons, mostly) [20:04] nothing i run forks anyway :) [20:04] is that compile time? [20:04] why do you want to run it under another init? [20:05] i'm switching distribution [20:05] it's "edit the source and recompile" time [20:05] basically comment out the getpid() check [20:06] ah, right. i'll experiment in a bit then [20:06] thanks. was just wondering if there was an easier way [20:07] not really [20:07] it's not something I want to support [20:07] since people will complain when things don't work because they're not init [20:08] hm. if it's just a matter of turnign a few thigns off and disabling the check, surely that's a reasonable compile time option [20:08] and anyone who builds one with that on will presumably know what they're getting [20:09] adding an option means supporting it ;) [20:09] "blah doesn't work when not pid 1" ... "so run as pid 1" ... "but there's an option to not run as pid 1" [20:10] i think you're overestimating the chance of that happening, but hey :) [20:12] perhaps [20:12] thanks anyway. i'll fiddle with it.