-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Jun 12, 2015 at 12:44:39PM +0100, Julian Brooks wrote:
> Hi Tomas,
>
> Cheers for the response.
>
> Ok - seems it would be useful to get to grips with 'chroot'.
Sorry -- I lost you: what has this to do with chroot?
> Also from recent posts it's not just me that finds printers a ball-ache.
I don't like printers either (the devices; the people are a quite nice
species, but on its way to extinction, but I disgress). As far as I can see
the problem (in my short reading, of the refs, I admit) hasn't got directly
to do with printers)
> Would be happy with a quick dirty fix tbh. I know the Right thing would be
> to track it down and sort it properly but could I, for example, locate
> what's setting the 'no limit' and set that to 10ms? Or something.
- From my reading of the refs, I'd try to see whether there are loads of
files in /tmp, compare your kernel version with the one mentioned on
one of the refs.
regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlV6zPoACgkQBcgs9XrR2kaKkQCeP0KWZr9UJ3goh3ClBLlFWdRX
ycoAn2ndtsRCVfNbcaSYZQ04Xhuu9m4D
=HCE0
-----END PGP SIGNATURE-----