Re: python dameon coredumps when started from boot, but not by hand
> Hmm, does changing the command_args line to this work: > command_args=3D"start 2>/tmp/waagent.log" > work? That is byte-for-byte identical to what I tried :-) It creates the file in /tmp, but the file remains empty. 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. -pete. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: python dameon coredumps when started from boot, but not by hand
> On 1 Nov 2019, at 23:26, Pete French wrote: > >> Hmm, does changing the command_args line to this work: >> command_args=3D"start 2>/tmp/waagent.log" >> work? > > 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.1-RELEASE schedule update
Hi Sergey, On Fri, Nov 01, 2019 at 01:44:18PM +, Sergey A. Osokin wrote: > Hi Glen, > > hope you're doing well. > You as well. > At the moment we have graphics/drm-fbsd12.0-kmod port for 12.0. > I hope in most cases it's enough for RELENG_12 branch, however > just to avoid a potential confusion I see the following options > we can do: > > - create a new port for 12.1 only > - rename the existing port to drm-fbsd12-kmod > - rename the existing port to drm-fbsd12.1-kmod (in case of 12.0 EoL) > What about using the meta-port and keying off of OSVERSION? (Personally I have no real preference either way, nor with any of the solutions you propose above.) > Also, since this is repeatable thing for every upcoming release > we can add this point to the check list and release scheduling. > Yes, good idea. Just let us know how you want to proceed, and we can add a note to the documentation. Glen signature.asc Description: PGP signature
