I do wonder about that message in the nohup.out file of my tinderbox - which might indicate, that those messages comes from stderr or so (but I *thought* I'd catched all of them) So /me wonder if there's some magic in the ebuild (process) here ?
Build log? emerge --info?
the issue is gone now - and I'm not really sure what triggered it. The odd thing is that I do catch all stdout/stderr in my tinderbox script from emerge. Maybe except for those where the parent pid crashed and then the child process goes directly to init 1 ?
