On Wed, 8 Dec 2021 16:48:08 -0500
Zach DeCook <zachdecook@xxxxxxxxxx> wrote:
> By flushing the output, iio_event_monitor can be more useful to programs
> chained along with it.
>
> iio_event_monitor stk3310 | awk '/rising/{system("my_unlockscreen.sh")} /falling/{system("my_lockscreen.sh")}'
>
> Without this flush, the above example would buffer a number of events,
> then after a while run the lock/unlock scripts several times.
>
> Signed-off-by: Zach DeCook <zachdecook@xxxxxxxxxx>
Seems sensible to me.
Applied to the togreg branch of iio.git and pushed out as testing for 0-day to poke at
it (possibly - no idea what it does with tools patches :)
Jonathan
> ---
> tools/iio/iio_event_monitor.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/iio/iio_event_monitor.c b/tools/iio/iio_event_monitor.c
> index 0076437f6..b94a16ba5 100644
> --- a/tools/iio/iio_event_monitor.c
> +++ b/tools/iio/iio_event_monitor.c
> @@ -279,6 +279,7 @@ static void print_event(struct iio_event_data *event)
> printf(", direction: %s", iio_ev_dir_text[dir]);
>
> printf("\n");
> + fflush(stdout);
> }
>
> /* Enable or disable events in sysfs if the knob is available */
