Bug 13065
Summary: | ks-script does not write postScript file | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Karl Burkett <burkett> |
Component: | anaconda | Assignee: | Erik Troan <ewt> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-07-07 21:00:10 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
Karl Burkett
2000-06-26 16:20:08 UTC
Placed a comment in front of os.unlink(path) at the end of todo.py and it worked. This seems to be the cure, though I don't understand why it should work this way. NEW INSITE INTO THE PROBLEM: Everything works just fine inside anaconda. I've found that the dificulty is happening because this version of todo.py attempts to clean-up after it's self by removing the ks-script file from /tmp. This is behavior that was not done on the version of anaconda that came with RedHat 6.1. In general, I found that having the ks-script left on the server was a good thing because I could then edit the script and run it again as a debugging step. Not a complaint, just an observation. Might want to leave a way to tell anaconda to not remove the ks-script file. Now in my version of the ks-script (this is long script of many lines) I have the script move the ks-script file into /var/log to preserve a record of what was done to the machine at installation time. This did not create a problem prior to this time because anaconda did not try to remove the file, but now with RedHat 6.2 anaconda does try to remove the file. I've changed my script to copy ks-script to /var/log, rather than move the file. This should take care of the problem, though, if I may suggest, making a test for the existance of the ks-file prior to attempting to unlink it might be a prudent think to do. Please close out this problem when you have a chance. Thanks. This has been fixed -- thanks for the info. |