Comments on: Radmind: converting to case-insensitive transcripts

By: Jeff Kelley

Jeff Kelley — Wed, 25 Jun 2008 22:34:14 +0000

These days we still have it as a pre-apply script, but I’m not sure how often we run into this issue (because the script would touch the file). We’re using case-insensitive, relative transcripts exclusively still.

By: Andrew Mortensen

Andrew Mortensen — Tue, 24 Jun 2008 23:07:17 +0000

I wrote that script when I was making the transition to case-insensitive transcripts in the Mac environment at Umich. I recall re-sorting the local copies of the transcripts before running the update. The trick was to do it without triggering ktcheck updates. Jeff, how are you using the script these days?

By: GregN

GregN — Tue, 24 Jun 2008 21:21:43 +0000

Neat. This should allow you to store only one version of the transcripts/loadsets on the server, and then dynamically resort as needed locally. Is that what you are doing?

By: Jeff Kelley

Jeff Kelley — Tue, 24 Jun 2008 21:15:29 +0000

That’s a good way to handle it server-side. We do something similar, but instead we touch the file on the hard drive before running lapply in a pre-apply script:

#! /bin/sh

# work around a hardlink ordering problem that occurs
# when a hardlink’s source is case-insensitively
# alphabetically greater than the target. E.g:
#
# h ./usr/share/man/man3/atomic.3 ./usr/share/man/man3/OSAtomicAdd32.3
#
# If the source doesn’t exist, and we run case-
# insensitively, the hardlink will fail because
# there’s nothing to link to.
#
# The workaround checks for such lines, and touches
# the source file, preventing hardlink errors.

PATH=/bin:/usr/bin; export PATH

trans=”$1″

if [ -z "${trans}" ]; then
logger -i -t $0 No arguments
exit 0
fi

cat “${trans}” | awk ‘{ if ( $1 == “h” ) { \
if ( tolower($2) < tolower($3) ) { \
if ( system( “test -e ” $3 ) != 0 ) { \
system( “touch ” $3 );
} \
} \
} \
}’

exit 0