-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/08/13 02:59, Andy Wettstein wrote:
> If proctrack/cgroup is not being used, I don't think it is possible > to properly track a process that does this. Since proctrack/cgroup > can reliably track all PIDs for a step, then I think it should be > able to track this. As I understand it Moe was saying that jobacct_gather/cgroup is buggy, not proctrack/cgroup. We are using proctrack/cgroup here in production on our x86 system that just went live and it seems to be working so far (no users have screamed yet). We did try jobacct_gather/cgroup but as Danny and Moe said it doesn't collect information, possibly (as Ralph postulated in a thread I started) because of confusion over signed/unsigned values (I was seeing negative values of memory use reported for some cases). All the best, 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/ iEYEARECAAYFAlIK2AMACgkQO2KABBYQAh8r2ACfa/A6Ktwcp+bUAWD7yWDOqEYR LW0Anj54UDj0XJixUMlNYRIWa1iOXTsb =+ddy -----END PGP SIGNATURE-----
