Hi,
I encountered the same problem. We have our home directories mounted via
automount. Whenever a user starts acroread in his/her home direcrectory
we receive this error message. My guess is that this error occurs due to
the porting from a windows environment, hence the backslash and
automount doesn't recognize AdobePanose.db as aseparate directory, thus
trying to mount the home thing: home-dir+AdobePanose.db .
In the starting script 'acroread' (ususally in /usr/X11R6/bin) it says:
<snip>
#
# Get the current working directory.
# Try to avoid automounter directories by checking
# if $HOME or $PWD is the same directory as pwd,
# and removing the automount directory component.
#
cwd="`pwd 2> /dev/null`"
if [ -z "$cwd" -o ! -d "$cwd" ] ; then
echo "ERROR: Cannot determine current directory."
exit 1
fi
if [ "$HOME" -a -d "$HOME" ] && [ "`cd / ; cd "$HOME" ; pwd`" = "$cwd" ]
; then
cwd="$HOME"
elif [ "$PWD" -a -d "$PWD" ] && [ "`cd / ; cd "$PWD" ; pwd`" = "$cwd" ]
; then
cwd="$PWD"
fi
if [ "$cwd" != / -a "${AUTOMOUNT_DIR=/tmp_mnt}" ] ; then
tmp="`expr "$cwd" : "$AUTOMOUNT_DIR"'/(.*/)'`"
if [ "$tmp" -a -d "$tmp" ] ; then
if [ "`cd / ; cd "$tmp" ; pwd`" = "`pwd`" ] ; then
cwd="$tmp"
fi
fi
fi
PWD="$cwd"
export PWD
<snap>
but this doesn't seem to work. Hence my quick and dirty workaround is a
modified acroread startup script. It checks whether we started acroread with
a file argument, that is a file with a .pdf extension. If so, we add a full
path to the argument. This works of course for relative paths to the file,
only.
Then we change to the root directory. This ensures, we are not in any
automounted directory. The idea is pretty simple and the script modifications
as well, but it seems to work.
These are the modifications I have done to the acroread script, starting from
approx. line 350
#
# Set the command. Process any debug flags and exec.
#
# New variable
COMMAND=${1+"$@"}
# Check, whether we have command line arguments.
# If so, check whether it is a pdf document and add the full path
# to the file
if [ $# -eq 1 ] && [ -z "${1##/*.pdf}" ] ; then
COMMAND=$PWD/${1}
fi
# Now change into the root dir, hence avoiding automounted
# directories
cd /
ACRO_EXEC_CMD="$ACRO_INSTALL_DIR/$ACRO_CONFIG/bin/$cmd"
if [ "$1" = "-DEBUG" ] ; then
if [ $# = 1 ] ; then
export ACRO_EXEC_CMD
exec "$SHELL"
else
shift
exec $COMMAND "$ACRO_EXEC_CMD"
fi
fi
if [ -f "$ACRO_EXEC_CMD" ] ; then
exec "$ACRO_EXEC_CMD" $COMMAND
else
echo "ERROR: Cannot find $ACRO_EXEC_CMD"
echo " $prod not installed for this configuration, \"$ACRO_CONFIG\"."
exit 1
fi
### Change back into old Dir. Do we need this?
cd -
Hope this helps.
Cheers,
Hauke
Am Freitag, 22. Februar 2002 10:17 schrieb Heinrich Rebehn:
> Hi,
>
> We are using V 4.0.0 on linux 2.4.16, Debian woody.
>
> When one of our users uses acrobat reader, it tries to access
> /home/boehnke\\AdobePanose.db/
> This is quite strange, but the reaction of autofs is even more strange:
>
> automount[25311]: >> mount: special device /dev/boehnkeAdobePanose.db does
> not exist automount[25311]: mount(generic): failed to mount
> /dev/boehnkeAdobePanose.db (type auto) on /home/boehnke\\AdobePanose.db/
>
> The automount entry for /home/boehnke is:
>
> boehnke antsrv1:/export/homes/wiss/boehnke
>
> There are no entries in the auto.home map that point to /dev
> auto.home is accessed via LDAP.
>
> Any ideas?
--
Dipl. Phys. Hauke Stephan Busch
Technische Universit�t Darmstadt
Institut f�r Angewandte Physik
Hochschulstra�e 4a
64289 Darmstadt
Germany
Tel.: +49-6151-163379
PGP: www.pgp.net/wwwkeys.html
