so i had another systat complete freeze, this time remotely, so again, no dump...
sorry about another useless report, but looking at the mailing list looks like other people are experiencing hangs during disk activity. (i am speculating in this direction simply because systat's first screen after starting is the disk activity.) what kind of bug could be triggered by a process started as non-root that kills the whole system is the 20 euro question of course. as nowadays virtually everyone is in X, i think i am not the only who has difficulties getting panic messages. at any rate, i am just writing this to perhaps have an openbsd systat day (together with a towel, being douglas adams' death anniversary) and simply run systat randomly on as many machines as possible. if absolutely noone else speaks up, i'll just assume any hw of mine is simply cursed and i am d.n.a.lusional. -f -- i may be wrong, but i'm never in doubt!
