* patch by Nico Erfurth:

Linux shows a similar behaviour as BEOS in this test. The time gets set to the
next day to around 12:00. While the problem only shows when running the
test-suite as root, it's still annoying when it happens.

git-svn-id: trunk@21434 -

tests/test/units/dos/tdos2.pp

@@ -246,6 +246,7 @@ Begin
  WriteLn(' Note: GetTime should return the same value as the previous test.     ');
  WriteLn('----------------------------------------------------------------------');
 {$ifndef beos}
+{$ifndef linux}
  {This should be disabled under BeOS : maybe this is a BeOS bug (or a feature ?) 
   in stime function.
   When you set 36 hours, the time AND the date are changed
@@ -253,9 +254,12 @@ Begin
   36 hours in the future from the begining of the starting day, more or less
   depending on your timezone.
   For example in Paris, in summer (2 hours from GMT time zone),
-  this call set the clock to 14:<Minute>:<Second>:<Sec100> the next day !}
+  this call set the clock to 14:<Minute>:<Second>:<Sec100> the next day !
+  Linux shows the same behaviour.
+  }
  SetTime(36,Minute,Second,Sec100);
  CheckDosError(0);
+{$endif}
 {$endif}
  GetTime(Hour1,Minute1,Second1,Sec1001);
  CheckDosError(0);