.
>
> After having stopped chronyd, please run the command below when using the
> 'bindacqdevice' directive and attach the chronyd_debug.txt file.
>
> # strace -o chronyd_debug.txt chronyd -d -F -1
OK, I did some more testing on my so-called fix: SO_BINDTOADDRESS define
statement made no
Got a bit further when I myself included `#define SO_BINDTODEVICE 1` to the
`config.h` that `configure` created.
Then I noticed that `configure` underwent a Redhat overhaul.
Missing the maintainer’s `configure.ac` so we can’t readily fix this. Punt
this bug upstair.
> On Sep 29, 2021, at
Summary:
The syscall filter daemon option flag -F is the cure.
Using '-F 0' to disable the syscall filter works. No other settings are
workable.
A summary table:
Chrony -- daemon flags used --
Version -F0 -F1 -F-1
--- -- -- --
4.0-9ok SIGSYS SIGSYS
>> Trying attachment again.
>
> Thanks. To see what happens when blocking only a small number of specific
> syscalls, could you please run the following command and attach the
> chronyd-debug.txt file?
>
> # timeout 10 strace -o chronyd-debug.txt -e trace=setsockopt chronyd -d -F 2
Le 2021-09-28 12:54, S Egbert a écrit :
> Trying attachment again.
Thanks. To see what happens when blocking only a small number of specific
syscalls, could you please run the following command and attach the
chronyd-debug.txt file?
# timeout 10 strace -o chronyd-debug.txt -e trace=setsockopt
Control: tags -1 - upstream + moreinfo
Control: severity -1 important
Hi,
Le 2021-09-27 17:31, Steve Egbert a écrit :
> Package: chrony
> Version: 4.0-8
> Severity: critical
> Tags: upstream
> X-Debbugs-Cc: s.egb...@sbcglobal.net
>
> Dear Maintainer,
>
>
> Wanted to use the 'bindacqdevice'
Package: chrony
Version: 4.0-8
Severity: critical
Tags: upstream
X-Debbugs-Cc: s.egb...@sbcglobal.net
Dear Maintainer,
Wanted to use the 'bindacqdevice' due to my host having a dynamic IP interface.
Using that 'bindacqdevice' directive keyword anywhere in my
/etc/chrony/chrony.conf file
7 matches
Mail list logo
