David et al, We've just discovered that in LiS-2.15 (I haven't checked other versions but we've not seen this symptom before) the STREAM head put routine queues all messages (lis_strrput) including M_FLUSH. This causes the service routine to flush the stream head read queue of all messages that came before AND AFTER the M_FLUSH message was sent upstream.
Is this correct or desired behaviour? Shouldn't the lis_strrput process the M_FLUSH message immediately rather than defer it to the service routine? Regards, Ragnar Paulson _______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
