[The prefix that is prepended to the name of message files when they are "removed" by rmm. This should typically be `,' or `#'.])dnl
dnl What method of locking to use?
+AS_CASE(["$host_os"],
+ [aix*|cygwin*|linux*],
+ [default_locktype="fcntl"; default_locking=FCNTL_LOCKING],
+ [freebsd*], [default_locktype="flock"; default_locking=FLOCK_LOCKING],
+ [default_locktype="dot"; default_locking=DOT_LOCKING])
+
AC_ARG_WITH(locking,
AS_HELP_STRING([--with-locking=@<:@dot|fcntl|flock|lockf@:>@],
[specify the file locking method]))
LOCKTYPE="fcntl"
AC_DEFINE(FCNTL_LOCKING, 1, [Define to use fnctl() based locking.])dnl
else
- LOCKTYPE="dot"
- AC_DEFINE(DOT_LOCKING)dnl
+ LOCKTYPE="$default_locktype"
+ AC_DEFINE_UNQUOTED($default_locking, 1)dnl
fi
dnl Should we use a locking directory?
fi
fi
+dnl Provide a way for distcheck to disable setgid_mail via
+dnl DISTCHECK_CONFIGURE_FLAGS.
+if test x"$DISABLE_SETGID_MAIL" != x -a x"$DISABLE_SETGID_MAIL" != x0; then
+ nmh_cv_dotlockfile_setgid=yes
+fi
+
dnl If mailspool is not world-writable and dotlockfile is not setgid,
dnl we need to #define MAILGROUP to 1 and make inc setgid.
if test x"$LOCKTYPE" = x"dot" -a x"$nmh_cv_mailspool_world_writable" = x"no" -a x"$nmh_cv_dotlockfile_setgid" != x"yes" ; then