|
Bugzilla – Full Text Bug Listing |
| Summary: | suse-ami-tools initscripts shoudn't use $ALL target | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Frederic Crozat <fcrozat> |
| Component: | Other | Assignee: | Bernhard Wiedemann <bwiedemann> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | crrodriguez, rjschwei |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Frederic Crozat
2011-07-13 16:43:03 UTC
Cornelius, who can take care of this now? Im taking a look, what a royal nasty hack is it !:) question, what the hell is sces-client which the init script wants in Should-Start ? sces-client is a tool that is used for SUSE Linux Enterprise inside of Amazon EC2. It needs to stay there. Bernhard, could you please take a look at this? I see /etc/init.d/amazon-late with # Provides: amazon-late # Required-Start: $all it is supposed to print ssh-key fingerprints to console after the other startup messages are done. So we could likely change it to # Required-Start: $network $remote_fs $syslog sshd if users would accept the change of ordering. Any way to make it run later (e.g. when gettys are about to be started)? There is a getty@tty1.service but not sure, how that could be used. you could run it with (if you use systemd .service file, shadowing the initscript when booting under systemd) After=getty@tty1.service but it will print the output after getty login prompt, so people might not see it. Another possibility could be to use a combination of After=default.target and a .timer file with OnActiveSec=0s (see /lib/systemd/system/systemd-readahead-done.* as an example). removing as blocker for bnc#696902 current version uses systemd service files, so it should be fine. |