Date: Sat, 2 Nov 2019 00:03:37 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Pete French <petefrench@ingresso.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: python dameon coredumps when started from boot, but not by hand Message-ID: <5D00F632-8BBA-4C8A-8D61-F85B336DA2F1@dons.net.au> In-Reply-To: <E1iQWTH-000Kbs-JL@dilbert.ingresso.co.uk> References: <E1iQWTH-000Kbs-JL@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 1 Nov 2019, at 23:26, Pete French <petefrench@ingresso.co.uk> = wrote: >=20 >> Hmm, does changing the command_args line to this work: >> command_args=3D3D"start 2>/tmp/waagent.log" >> work? >=20 > That is byte-for-byte identical to what I tried :-) It creates the = file > in /tmp, but the file remains empty. Oops, sorry :) > I think I need to look at the source code to work out whats up with it = (on > the github link in my original email). As I now know its one piece of = python > which attemopts to start another, and we know the bit started directly > from rc.d works, then this may not be something within BSD after all. It seems bad that the Python interpreter is calling abort, I would have = thought that doing so is pretty tricky to do from pure Python so finding = out why would be good.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D00F632-8BBA-4C8A-8D61-F85B336DA2F1>