On Wed, Sep 04, 2024 at 08:15:32PM +0200, Florian Obser wrote:
> On 2024-09-04 19:39 +02, Florian Obser wrote:
> > event_dispatch() in main(), frontend() and engine() returns 0.
> >
> > the man page says:
> >
> > In order to process events, an application needs to call
> > event_dispatch
On 2024-09-04 19:39 +02, Florian Obser wrote:
> event_dispatch() in main(), frontend() and engine() returns 0.
>
> the man page says:
>
> In order to process events, an application needs to call
> event_dispatch(). This function only returns on error, and should
> replace the event
event_dispatch() in main(), frontend() and engine() returns 0.
the man page says:
In order to process events, an application needs to call
event_dispatch(). This function only returns on error, and should
replace the event core of the application program.
which apparently is a
Hi,
Am 04.09.24 um 15:26 schrieb Alexander Bluhm:
On Wed, Sep 04, 2024 at 02:44:01PM +0200, Stefan Fritsch wrote:
Hi,
during network driver testing I sometimes do a stress test with
while true; do ifconfig vio0 -inet; done &
while true; do ifconfig vio0 inet autoconf; done &
while true; do if
On Wed, Sep 04, 2024 at 02:44:01PM +0200, Stefan Fritsch wrote:
> Hi,
>
> during network driver testing I sometimes do a stress test with
>
> while true; do ifconfig vio0 -inet; done &
> while true; do ifconfig vio0 inet autoconf; done &
> while true; do ifconfig vio0 -inet6; done &
> while true;
Hi,
during network driver testing I sometimes do a stress test with
while true; do ifconfig vio0 -inet; done &
while true; do ifconfig vio0 inet autoconf; done &
while true; do ifconfig vio0 -inet6; done &
while true; do ifconfig vio0 inet6 autoconf; done &
while true; do ifconfig vio0 down; done
