On Thu, Feb 14, 2019 at 9:44 AM Richardyusen <[email protected]> wrote:
> Hello,
> I installed busybox-1.30.0 on my mini Linux system, and when I tried to
> use runsvdir to launch a simple syslogd service, it gave the following
> error:
>
> runsv: fatal: unable to lock supervise/lock: function not implemented
busybox has no "unable to" text in its error messages
(we use shorter "can't"):
if (flock(svd[0].fdlock, LOCK_EX | LOCK_NB) == -1)
fatal_cannot("lock supervise/lock");
static void fatal_cannot(const char *m)
{
fatal2_cannot(m, "");
/* was exiting 111 */
}
static void fatal2_cannot(const char *m1, const char *m2)
{
bb_perror_msg_and_die("%s: fatal: can't %s%s", dir, m1, m2);
/* was exiting 111 */
}
So the message clearly isn't coming from busybox's runit...
anyway:
> I googled a bit and all I could find was errors saying "temporary
> failure" instead of "function not implemented". What function is not
> implemented? Could this be a busybox problem, or a problem with my kernel or
> libc? (I compiled my own kernel, and built my own toolchain based on
> musl-libc).
Looks like flock() is not implemented (disabled in kernel .config?)
>
> I did take a look at this link: https://github.com/MichielDerhaeg/build-linux
> Maybe it can offer some clues?
>
>
> Thanks a lot! I asked this on LinuxQuestions.org and nobody knows why...
>
> --Richard
>
>
>
>
>
>
>
>
> _______________________________________________
> busybox mailing list
> [email protected]
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
