Re: Bad system call

2021-01-18 Thread James Browning via devel
On Mon, Jan 18, 2021, at 4:19 PM Gary E. Miller via devel wrote: > But I agree someone that cares should fix it. > I think NTPsec should be completely rewritten as discrete units. I have a file of ramblings that is not ready for publication. > Thanks to you and James for you help. > Hal came

Re: Bad system call

2021-01-18 Thread Gary E. Miller via devel
Yo Hal! On Mon, 18 Jan 2021 16:02:53 -0800 Hal Murray wrote: > > How do I know I have seccomp running? I have always avoided it. > > Scan your config.h for SECCOMP > details in wscript -- search for seccomp Yup, there it is. I forgot it was on this host. > > How do I disable it? > >

Re: Bad system call

2021-01-18 Thread Hal Murray via devel
> How do I know I have seccomp running? I have always avoided it. Scan your config.h for SECCOMP details in wscript -- search for seccomp > How do I disable it? Stop configuring with --enable-seccomp > Looks like I had built NTPsec with --enable-seccomp a while back. glibc > upd

Re: Bad system call

2021-01-18 Thread Gary E. Miller via devel
Yo All! On Mon, 18 Jan 2021 15:37:01 -0800 "Gary E. Miller via devel" wrote: > > It looks like seccomp is blocking __NR_clock_gettime64. Try > > compiling with the list updated or sans seccomp? Looks like I had built NTPsec with --enable-seccomp a while back. glibc updated, and broke ntpd. E

Re: Bad system call

2021-01-18 Thread Hal Murray via devel
>> Have you tried strace or gdb? > strace attached. clock_gettime64(CLOCK_REALTIME_COARSE, {tv_sec=9136151223987077120, tv_nsec=18446744071541764330}) = 5 --- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_call_addr=0x76a9238c, si_syscall=__NR_clock_gettime64, si_arch=AUDIT_ARCH_ARM} --- cl

Re: Bad system call

2021-01-18 Thread Gary E. Miller via devel
Yo James! On Mon, 18 Jan 2021 15:10:53 -0800 James Browning via devel wrote: > On Mon, Jan 18, 2021, 3:04 PM Gary E. Miller via devel > wrote: > > > Yo Hal! > > > > On Mon, 18 Jan 2021 14:00:49 -0800 > > Hal Murray wrote: > > > > > > Ideas anyone? > > > > > > Have you tried strace or gdb?

Re: Bad system call

2021-01-18 Thread James Browning via devel
On Mon, Jan 18, 2021, 3:04 PM Gary E. Miller via devel wrote: > Yo Hal! > > On Mon, 18 Jan 2021 14:00:49 -0800 > Hal Murray wrote: > > > > Ideas anyone? > > > > Have you tried strace or gdb? > > strace attached. > > # strace -o strace ntpd -nN > It looks like seccomp is blocking __NR_clock_gett

Re: Bad system call

2021-01-18 Thread Gary E. Miller via devel
Yo Hal! On Mon, 18 Jan 2021 14:00:49 -0800 Hal Murray wrote: > > Ideas anyone? > > Have you tried strace or gdb? strace attached. # strace -o strace ntpd -nN RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave.,

Re: Bad system call

2021-01-18 Thread Hal Murray via devel
> Ideas anyone? Have you tried strace or gdb? -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: ✘Bad system call

2021-01-18 Thread Gary E. Miller via devel
Yo James! On Mon, 18 Jan 2021 12:37:26 -0800 James Browning via devel wrote: > On Mon, Jan 18, 2021, at 12:22 PM Gary E. Miller via devel > wrote: > > > Yo All! > > > > I have not been able to build/run ntpd on one system for a while. > > It used to work. No AppArmor. This is Gentoo stable.

Re: ✘Bad system call

2021-01-18 Thread James Browning via devel
On Mon, Jan 18, 2021, at 12:22 PM Gary E. Miller via devel wrote: > Yo All! > > I have not been able to build/run ntpd on one system for a while. It used > to work. No AppArmor. This is Gentoo stable. I recompiled the world > more than once just in case. The SD card is fine (for now). Try