root permissions conflict
Guest wrote on Aug 24, 2007
When I do a setinstrument to load the instrument parameters, that works just fine.
Next, I run ccdin to look at the keyword files and I get a ââ¬Å?ââ¬Âââ¬Â¦ expected.
I do the change and when I go to quit I get the standard ââ¬ÅDo you want to update the instrument file?ââ¬Â (yes)
If I say yes, I get
ââ¬ÅWarning: Cannot delete file (ccddb$kpno/direct.dat) and no changes are kept.
All of the iraf directories and files are owned by root and the directory structure permissions are 755.
All of the file permissions are set at 644.
I donââ¬â¢t see anything obvious in the .cl files for the instruments.
Weââ¬â¢re running V12.2, loaded via rpms from univ Arizona astro group.
Any ideas?
Post generated using Mail2Forum (http://www.mail2forum.com)
Next, I run ccdin to look at the keyword files and I get a ââ¬Å?ââ¬Âââ¬Â¦ expected.
I do the change and when I go to quit I get the standard ââ¬ÅDo you want to update the instrument file?ââ¬Â (yes)
If I say yes, I get
ââ¬ÅWarning: Cannot delete file (ccddb$kpno/direct.dat) and no changes are kept.
All of the iraf directories and files are owned by root and the directory structure permissions are 755.
All of the file permissions are set at 644.
I donââ¬â¢t see anything obvious in the .cl files for the instruments.
Weââ¬â¢re running V12.2, loaded via rpms from univ Arizona astro group.
Any ideas?
Post generated using Mail2Forum (http://www.mail2forum.com)
Mike Fitzpatrick wrote on Aug 24, 2007
CCDINSTRUMENT is trying to directly modify the files in the ccddb$ database directory, i.e. the ones owned by root. Unless you're logged in as root you can't change these as another user. You can still use the task to create the .dat file in a place where you can write (e.g. copy an existing entry), and then to use it you could simply set the ccdred.instrument parameter to e.g. home$myinst.dat
-Mike
-Mike
Last post on Aug 24, 2007