On Sat, Jun 22, 2019 at 4:08 AM Richard Purdie
wrote:
>
> On Fri, 2019-06-21 at 15:27 -0400, Jon Mason wrote:
> > syslogd and klogd can occasionally take too long to restart, which
> > causes tests to fail by starting before the log daemons are ready. To
> > work around this problem, poll for up
On Sat, 2019-06-22 at 09:12 +0100, Richard Purdie wrote:
> On Sat, 2019-06-22 at 09:08 +0100, Richard Purdie wrote:
> > On Fri, 2019-06-21 at 15:27 -0400, Jon Mason wrote:
> > > syslogd and klogd can occasionally take too long to restart,
> > > which
> > > causes tests to fail by starting before
On Sat, 2019-06-22 at 09:08 +0100, Richard Purdie wrote:
> On Fri, 2019-06-21 at 15:27 -0400, Jon Mason wrote:
> > syslogd and klogd can occasionally take too long to restart, which
> > causes tests to fail by starting before the log daemons are
> > ready. To
> > work around this problem, poll
On Fri, 2019-06-21 at 15:27 -0400, Jon Mason wrote:
> syslogd and klogd can occasionally take too long to restart, which
> causes tests to fail by starting before the log daemons are ready. To
> work around this problem, poll for up to 30 seconds on the processes to
> verify the old ones are
On Fri, 2019-06-21 at 15:27 -0400, Jon Mason wrote:
> syslogd and klogd can occasionally take too long to restart, which
> causes tests to fail by starting before the log daemons are
> ready. To
> work around this problem, poll for up to 30 seconds on the processes
> to
> verify the old ones are
syslogd and klogd can occasionally take too long to restart, which
causes tests to fail by starting before the log daemons are ready. To
work around this problem, poll for up to 30 seconds on the processes to
verify the old ones are killed and the new ones are up and running.
[YOCTO #13379]
