Update Locks Package Handling

[Billie Walsh]

On 01/12/2011 07:45 PM, Billie Walsh wrote:
> On 01/12/2011 04:56 PM, Clay Weber wrote:
>> there is more than one place for a lock file, if you run
>> sudo apt-get update or
>> sudo apt-get dist-upgrade
>> if there is a so-called stale lock file the error message will give 
>> the proper
>> filename and path.
>>
>> clay
>>
>
> Running sudo apt-get update goes through a bunch of reading packages 
> then comes up with this:
>
> "E: dpkg was interrupted, you must manually run 'sudo dpkg --configure 
> -a' to correct the problem."
>
> So you run "sudo dpkg --configure -a" and it does some stuff then 
> hangs on grub config. Sits there for hours or until you finally kill 
> it or shut off the computer. That's how the system got stuffed in the 
> first place.
>

Still trying to figure out what's going on.

Is there a command that tells you what process is running in the background?

How do you kill a process running in the background?

I'm sure it's been posted a bunch of times but I've never needed to know 
till now. And, I have no idea what to search for in the archive.

The reason I ask is because doing a "kdesudo dolphin" command to bring 
up Dolphin in admin mode and removing either apt/lock or dpkg/lock does 
no good because they just pop right back. This makes me wonder if dpkg 
is still running but never completing it's business, so to speak. When  
you try to remove the lock it reinstates it immediately.

I tried the "dpkg --configure -a" command again and just left it sit for 
about twenty-four hours and it was still hung on grub configure. I'm 
beginning to think there is something wrong with some part of grub 
install that dpkg can't resolve.

-- 
"A good moral character is the first essential in a man." George Washington

_ _...  ..._ _
_._  ._  .....  ._..  ...  .._