-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/07/13 08:10, Mark Hahn wrote:
> I would argue that this sort of restriction is BOFHish I think of it more as protecting user jobs from other users who are new to HPC and probably well meaning (or desperate to get jobs running). As the users project here get allocated service units and charged for compute time in those units we have a duty to make sure they are getting the time they've been allocated. Some of them are quick to let us know if a users job has managed to escape from Torque's cpuset controls for instance (we had a weird issue here that caused that for a bit). cheers! Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHwaGIACgkQO2KABBYQAh8C8wCcDlcJveYRCuYr88eSB24YxxMk RGIAni2n/6bM0BU9AfRMkBkBwBzd3gB6 =/dVY -----END PGP SIGNATURE----- _______________________________________________ Beowulf mailing list, [email protected] sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
