Bug 435056
| Summary: | needs better docs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> |
| Component: | upstart | Assignee: | Casey Dahlin <cdahlin> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | notting, rvokal, scott, vanhoof |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-05 00:30:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bill Nottingham
2008-02-27 02:01:29 UTC
What's the delivery mechanism we want to use? Just drop stuff in the docs folder? The Manpages do a pretty good job of describing the commands and the general workings, its just the job definitions where information is sparse (even I'm not certain what all is available). We could add a man event.d page that explained these. The event definition stuff is what I'm missing; there seems to be a lack of anything that describes how to write non-trivial events. For example, our prefdm script has: stop on runlevel [!5] but I'm unable to find anything that describes that syntax, or what other globbing/operators may be available, or variable substitutions, etc. That only got written because Scott wrote it :) We'll need him in on this methinks. Part of the reason that there's not much documentation on the job definition format is that it's been subject to change, and I didn't want people relying on anything more than the basic features documented on getting-started (even those changed with 0.3! :p) Documentation will be coming though, as soon somebody (me probably :-/) sits down and writes it -- code comes first tho :p For the record, the globbing is done with fnmatch() so follows glob(7) rules |