|
Bugzilla – Full Text Bug Listing |
| Summary: | New sort of RequiredStart | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jan Engelhardt <jengelh> |
| Component: | Basesystem | Assignee: | Dr. Werner Fink <werner> |
| Status: | VERIFIED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jan Engelhardt
2005-09-08 12:44:55 UTC
No it must not. Think twice you really do not need this. and therefore the LSB specs do not define this. Btw: The syslog _reqires_ networkl to be able to log over network to a remote log server, compare with the manual of syslogd. Well this wasnot related to syslog really. The feature request is basically to have a field to define depencendies. If these dependencies are not started, that's ok, but the boot order is important. Not for syslog, but for general apps. Believe me: the kausal order is always correct, if you switch between cause and impact you'll get the backward order. Think about make and Makefiles. I do not know what you wanted to say by that, but to put it concretely: I've got my firewall which currently has RequiredStart: $network named named, because it resolves hostnames. However, there are also linux clients without a named and just libresolv (/etc/resolv.conf), therefore, the "named" in the RequiredStart would be a hindrance. Resolving would work anyway because of the properly setup resolv.conf. Use Should-Start |