Date: Sat, 28 May 2005 14:31:45 -0700 From: Kris Kennaway <kris@obsecurity.org> To: K?vesd?n G?bor <gabor.kovesdan@t-hosting.hu> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Abort rap from cron Message-ID: <20050528213145.GA68641@xor.obsecurity.org> In-Reply-To: <4298DA78.3020504@t-hosting.hu> References: <4298A622.3020100@t-hosting.hu> <20050528174949.GA48170@xor.obsecurity.org> <4298DA78.3020504@t-hosting.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
--NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 28, 2005 at 10:54:16PM +0200, K?vesd?n G?bor wrote: > It is a single processor system. Those cron scripts are to verify=20 > whether my processes are run. So, there isn't such simultaneous runs.=20 > They are small scripts, that send a SIGCHLD to the processes they are=20 > responsible for, and if they don't find the processes running, they=20 > restarts them. I've been surprised because this hadn't happened before I= =20 > upgraded to 5.3-p13. Not only my scripts caused this, even the atrun,=20 > which is a default entry in the stock /etc/crontab. OK, some binary is probably calling abort() explicitly then. You should have a record in your syslog. Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCmONBWry0BWjoQKURAicCAJ94a7w/tTICKIanx+yg6aMyoTBwQgCgkmXA kK79LD538zkb/M6jLkUU7bY= =DPHR -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050528213145.GA68641>