Hello, Well, that's what I get at least on my 32-bit GNU/Linux system (Gentoo Linux, which means GNU libc). For example:
* s6-ftrig-wait dies with a 'fatal: unable to ftrigr_startf: Value too large for defined data type' message. * s6-supervise dies with a 'fatal: unable to iopause: Value too large for defined data type' message. * s6-svscan issues a 'warning: unable to iopause: Value too large for defined data type' message and then execs into its 'crash' script. This all means libc functions failing with EOVERFLOW, right? The last versions that didn't behave this way were s6-2.0.0.1 + skalibs-2.1.0.0. Maybe there is a problem somewhere in the time manipulation functions that were changed in skalibs-2.2.0.0? These are the skalibs sysdeps: target: i686-pc-linux-gnu clockrt: yes clockmon: yes endianness: little sizeofushort: 2 sizeofuint: 4 sizeofulong: 4 sizeofgid: 4 sizeoftime: 4 accept4: yes ancilautoclose: no cmsgcloexec: yes devurandom: yes eproto: yes eventfd: yes flock: yes getpeereid: no sopeercred: yes getpeerucred: no ipv6: yes malloc0: yes msgdontwait: yes nbwaitall: yes openat: yes linkat: yes pipe2: yes posixspawn: yes ppoll: yes revoke: no sendfile: yes setgroups: yes settimeofday: yes signalfd: yes splice: yes strcasestr: yes uint64t: yes devrandom: yes Thanks, G.
