On Thu, 2008-01-17 at 23:24 +0100, Michael Biebl wrote: > 2008/1/17, Scott James Remnant <[EMAIL PROTECTED]>: > > On Thu, 2008-01-17 at 12:37 +0100, Michael Biebl wrote: > > > 2008/1/16, Scott James Remnant <[EMAIL PROTECTED]>: > > > > On Wed, 2008-01-16 at 12:45 +0100, Michael Biebl wrote: > > > > > 2008/1/16, Scott James Remnant <[EMAIL PROTECTED]>: > > > > > > Disable a job from its definition, instead of just deleting it. > > > > > > > > > This approach has some problems though: > > > 1.) It changes the md5sum of the file. This results in dpkg prompts on > > > package upgrades. > > > > > > > > > I have again become unconvinced of the usefulness of this, > > > > > > instead favouring something more like "profiles" or "flags" > > > > > > where jobs can be disabled and enabled en-masse. > > > > > > > >> The disabling would have to be external to the job files. > > > Correct, and it's the only sensible way imho. > Ah, we appear to have reached the beginning of this conversation ;)
> Now, for the implementation, I can think of different solutions: > 1.) Use symlinks and profiles/runlevel directories. Proven, rather > easy to handle. Scott doesn't like them though ;-) > You end up with a maintenance burden for an all-in "profile", and if you have a lot of profiles, you have a lot of directories and a lot of symlinks. > 2.) Use the x bit to mark if a job is disabled or not. Imho a bit > hackish. Doesn't allow more complex schemes like different > profiles/runlevels. > Abuse of the bit. > 3.) extended attributes. Store the information if a job is > disabled/enabled (for a given profile/runlevel) using user_xattr. > Requires fs support. > Eurgh. > 4.) Define runlevels/profiles using files. Wasn't Alex hacking on this? > Yeah, dunno how far he got though? Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
