I'm not able to reproduce this using the current codebase.
Note that exim_tidydb needs run like this:
$ /usr/sbin/exim_tidydb /tmp misc
Tidying Exim hints database /tmp/db/misc
The exim4-base script itself has changed over the years, and I suspect
it's fixed whatever the original problem is. For reference, the
corresponding code now looks like this:
# if we reach this, invoking exim_tidydb from start-stop-daemon has
# failed, most probably because of libpam-tmpdir being in use
# (see #373786 and #376165)
find $SPOOLDIR/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' \
-or -type f -printf '%f\0' | \
runuser --shell=/bin/bash \
--command="xargs -0r -n 1 /usr/sbin/exim_tidydb $SPOOLDIR > /dev/null"
\
Debian-exim
Is the original issue still reproducible with Ubuntu 18.04 or 20.04?
** Changed in: exim4 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832030
Title:
Cron error from exim4-base: "run-parts: /etc/cron.daily/exim4-base
exited with return code 123"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/832030/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
