5 Mar
2009
5 Mar
'09
10:42 a.m.
Mark Rogers wrote:
Is there anything I can do to find out where it's stuck to fix it? I haven't killed the process yet (although I think I'll have to pause it to get some CPU back).
Curiouser and curiouser....
I went to bring the job into the foreground so that I could pause (Ctrl-Z) it [*]
$ jobs [1]+ Stopped sudo updatedb (wd: ~) $ fg 1 sudo updatedb (wd: ~) [sudo] password for mark:
So it looks like I must have run sudo updatedb & .. and sudo needed my password, which it couldn't get in the background. Understandable in itself, but why would it need such a high cpu level to do nothing?
[*] Incidentally, is there an equivalent to fg for pausing a background job?
--
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0845 45 89 555
Registered in England (0456 0902) at 13 Clarke Rd, Milton Keynes, MK1 1LG