[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: Runit Fatal Error: Function Not Implemented
From: Denys Vlasenko <vda.linux () googlemail ! com>
Date: 2019-02-19 14:28:55
Message-ID: CAK1hOcNoeTac_OVe+ofS67xTm9t=t=cTRWei7RS1p2qo3DjYkw () mail ! gmail ! com
[Download RAW message or body]
On Sat, Feb 16, 2019 at 7:29 AM Richardyusen <richardyusen@126.com> wrote:
> Hello,
> Sorry, I typed the error message from my memory. I ran it again and the exact
> message did use the word "can't" instead of "unable to". I lost my previous
> busybox build config, so I rebuilt a new one following the same procedure I
> used last time. I checked that "CONFIG_FLOCK" is set to "y" in the busybox
> .config file
This enables flock *applet*. This has nothing to do with the problem.
, however I didn't manage to find any "flock" related fields in the
> kernel config file. I put this newly compiled busybox into the system, and
> it gave me the exact same error!
Since now you have flock applet, let's see what happens when flock()
is called. Try this:
$ strace busybox flock README busybox true
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
prctl(PR_SET_NAME, "busybox") = 0
getuid32() = 0
open("README", O_RDONLY|O_CREAT|O_NOCTTY|O_LARGEFILE, 0666) = 3
flock(3, LOCK_EX) = 0
vfork() = 6787
wait4(6787, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 6787
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=6787,
si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
exit(0) = ?
+++ exited with 0 +++
What do you see?
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic