satprep_prepare_maintenance.py is not working
Closed this issue · 7 comments
./satprep_prepare_maintenance.py -k -a auth -g Test_for_satprep -K errata-snapshot-report-localhost-20151217-1433.csv
Haha, you're funny.
Can you have a look please
./satprep_prepare_maintenance.py -V errata-snapshot-report-localhost-20151217-1433.csv
Traceback (most recent call last):
File "./satprep_prepare_maintenance.py", line 498, in
main(options)
File "./satprep_prepare_maintenance.py", line 379, in main
verify()
File "./satprep_prepare_maintenance.py", line 51, in verify
myLog = open(myPrefix+"_satprep.vlog", "r+")
IOError: [Errno 2] No such file or directory: '20151219_satprep.vlog'
Is the user you're using for running the script allowed to create files in the directory?
Does this issue persist for you in the latest release of satprep?
I am ruuning using root. I did not check the latest one. Can i run using
any other user than root ?
On Monday, 18 April 2016, Christian Stankowic notifications@github.com
wrote:
Is the user you're using for running the script allowed to create files in
the directory?
Does this issue persist for you in the latest release of satprep?—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#52 (comment)
Sent from my iPhone
As long as this user has the rights to write in the current directory and also to /tmp you can use any user. :)
Thank you for your prompt reply :)
On Tue, Apr 19, 2016 at 4:44 AM, Christian Stankowic <
notifications@github.com> wrote:
As long as this user has the rights to write in the current directory and
also to /tmp you can use any user. :)—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#52 (comment)
You're welcome!
Let me know if you need further assistance.
Best regards!
Sure will do. Thanks for all your help
On Mon, Apr 25, 2016 at 12:23 AM, Christian Stankowic <
notifications@github.com> wrote:
You're welcome!
Let me know if you need further assistance.
Best regards!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#52 (comment)