[OpenWrt-Devel] flock clash with msmtpq-ng-mta

Marcel Telka marcel at telka.sk
Fri Jan 4 02:14:12 EST 2019


After upgrade from LEDE 17.01.4 to OpenWrt 18.06.1 I noticed that mailq from
the msmtpq-ng-mta package no longer works:

# mailq
flock: unrecognized option: w
BusyBox v1.28.4 () multi-call binary.

Usage: flock [-sxun] FD|{FILE [-c] PROG ARGS}

[Un]lock file descriptor, or lock FILE, run PROG

	-s	Shared lock
	-x	Exclusive lock (default)
	-u	Unlock FD
	-n	Fail rather than wait
logger: unrecognized option: i
BusyBox v1.28.4 () multi-call binary.

Usage: logger [OPTIONS] [MESSAGE]

Write MESSAGE (or stdin) to syslog

	-s	Log to stderr as well as the system log
	-t TAG	Log using the specified tag (defaults to user name)
	-p PRIO	Priority (numeric or facility.level pair)

The problem is that busybox 1.28.4-2 ships /usr/bin/flock (and it lacks support
for the -w option) which was not the case for busybox 1.25.1-4 (in 17.01.4).
The /usr/bin/flock was just not there.  Apparently, logger is a problem too.

So either mailq should be changed to do not expect the -w option for flock, or
flock should be enhanced to support -w, or the busybox package should stop to
deliver flock.

To workaround this issue on an already running device just simply remove the
/usr/bin/flock symlink.


| Marcel Telka   e-mail:   marcel at telka.sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel at jabber.sk |

openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list