A thin client cannot boot while a new NDB image is being compressed
Bug #345914 reported by
Guillaume Pratte
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LTSP5 |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Before compressing the new image for thin clients, the old one is moved to $NAME.tmp, making the thin clients unable to boot during the compression of the image.
Creating the new image with a different name then renaming it to the name used in inetd.conf would avoid this problem.
Related branches
| Changed in ltsp: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Marc Gariépy (mgariepy) wrote | #1 |
| Changed in ltsp: | |
| status: | Triaged → Fix Released |
| status: | Fix Released → Fix Committed |
| Changed in ltsp: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
http://