Horst Schirmeier dbff3ab236 jobserver: exit completely when socket ops fail ...

When socket(2), setsockopt(2), bind(2), listen(2), or accept(2) return an
unexpected error status, it is usually not a good idea to let the campaign
continue.  This is especially a problem as the perror(3) message gets lost
in normal campaign output and may be missed by the user.

Change-Id: I92747174e0706a613bedd8c6664cc8d888e07533

2014-03-05 16:48:37 +01:00

..

core

jobserver: exit completely when socket ops fail

2014-03-05 16:48:37 +01:00

experiments

ecos: modifications for mibench benchmarks

2014-02-25 13:32:56 +01:00

plugins

serialoutput: cleanup

2014-02-25 13:32:55 +01:00

CMakeLists.txt

DatabaseCampaign: abstract campain for interaction with MySQL Database

2013-04-02 09:52:42 +02:00

dummy.cc

FailBochs build process reversed

2012-06-29 22:22:41 +00:00