Opened 12 years ago
Closed 11 years ago
#3 closed defect (wontfix)
oml2-server-hook.sh attached to tutorial instructions will not work with non-tutorial (e.g. gimiXX) iRODS accounts
Reported by: | johren@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | OML | Version: | SPIRAL4 |
Keywords: | Cc: | ||
Dependencies: |
Description
The oml2-server-hook.sh script that is attached to the tutorial instructions and installed on emmy9 will only push results to the appropriate account in irods if the slice name and the user's iRODS account username start with gimi[0-9]. It assumes that the zone on the iRODS server is geniRenci.
NAME=${DBFILE:12:6}; FILE=${DBFILE:12}; LENGTH=${#FILE} SLICE=${FILE:0:$LENGTH-4} DATE=
date
${IPUT} ${OPTION} ${DBFILE}if $NAME =~ ^gimi[0-9] ?; then
echo "Entered..."
ichmod -M own $NAME /geniRenci/home/$NAME/$FILE iput -f ${DBFILE} /geniRenci/home/$NAME/$FILE; imeta add -d /geniRenci/home/$NAME/$FILE Date ${DATE} imeta add -d /geniRenci/home/$NAME/$FILE UserName? $NAME imeta add -d /geniRenci/home/$NAME/$FILE SliceName? $SLICE
fi
The hook script is also very specific to the configuration of the OML server in that it assumes the path to the DB file contains 12 characters. It isn't clear in the instructions that the user will need to adjust the hook script if they want to use it on their own OML server.
No longer an issue. Cleaning up old tickets as we revive the ticket tracking in GIMI.