Re: Strange behaviour of bash script in crontab
Op maandag 27 juni 2022 19:03:23 CEST schreef Freek de Kruijf: I did twice a "strace dig smtp.gmail.com", one with the issue and the other one without the SIGTERM issue. I provide the last few lines of the output of these commands: --- with SIGTERM issue --- ;; Query time: 0 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Mon Jun 27 18:46:47 CEST 2022 ;; MSG SIZE rcvd: 59 <unfinished ...>) = ? +++ killed by SIGTERM +++ Terminated --- without SIGTERM issue --- ;; Query time: 0 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Mon Jun 27 18:59:12 CEST 2022 ;; MSG SIZE rcvd: 59 {si_signo=SIGTERM, si_code=SI_USER, si_pid=16663, si_uid=1001}, NULL, 8) = 15 (SIGTERM) write(8, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0xffffba4f2020, FUTEX_WAKE_PRIVATE, 1) = 1 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 close(6) = 0 close(7) = 0 close(8) = 0 close(3) = 0 munmap(0xffffba3a4000, 1314816) = 0 write(10, "\0\0\0\0\377\377\377\377", 8) = 8 epoll_ctl(11, EPOLL_CTL_DEL, 9, 0xffffc8568268) = 0 close(11) = 0 munmap(0xffffb9378000, 172032) = 0 futex(0xffffba4f30a0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0xffffba4f3020, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0xffffb9ba20b0, FUTEX_WAIT, 16665, NULL) = -1 EAGAIN (Resource temporarily unavailable) munmap(0xffffba4e5000, 266240) = 0 futex(0xffffbb37408c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0xffffbb37404c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0xffffbb373f1c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 exit_group(0) = ? +++ exited with 0 +++ -- fr.gr. member openSUSE Freek de Kruijf
participants (1)
-
Freek de Kruijf