Frustratingly, my other recent questions (on the same project, but not the same problems) have elicited a similar response. It seems that the more exotic parts of Linux computing are unknown by most individuals, which is a shame, since there is so much potential. Like getting Negotiate authentication working with CUPS printing - no replies there after nearly a week.

Ah well. If there is any activity here then I will certainly be interested in it. Thanks again for your unwavering support.

Your Welcome

And; should the folks @Ubuntu finally answer me you'll be the first to know-

Indeed; which is one of the reasons I borrowed from my library "Upgrading And Repairing PC's" By: Scoot Mueller Once fully educated on How a processor, motherboard and power supply really works and How the system makes calls to the devices I should be able to practice that potential that your talking about. And further apply thought into how to fix these annoying issues. (it's my hope anyhow)
I've been running Linux about 4 years now and I'm sure not stopping the train now-

In regard to:
As your probably already aware; the GPG keys guarentee that the pkg comes from the repo it is claimed to come from. So since the GPG keys provide some level of integrity I'm wondering if there is some kind of forged or broken issue going on?

No, GPG keys would (or at least shouldn't) create issues. It could be the keytab however. Or a broken implementation of the IPP backend. Or privilege issues. I don't know, and it seems that Server Fault doesn't know either.

Ok, just thought GPG because some folks have bad practices and think forging is fun.

If I have time I'll do re-search on (broken) 'implementation of the 'IPP' and "reports about authentication issues' may provide a few hints or ideas of what might be going on-

Just a quick search already and I found about 5 articles on Implementing Server Fault Tolerance and Strategies.

The thing about re-search is it may take weeks. Occasionally (with serious critical thinking) I'll find the workaround. In the mean time I too; like you have other fires to put out.

p rob1:

Hi:

Sorry, still no word and it's been almost 3 months.

They have never not responded to me. I'm not only disappointed but sorry I can't help-
I did what I could-

Well you have been the only person to show any interest in my question, on this site and others. For that alone you deserve lots of kudos, especially since you remembered about this thread after 3 months. Yes, it's a shame that there isn't a solution, but there are other methods to accomplish what I want.

Thanks for the compliment; rob-

As a last thought:
If it's possible set Windbind so it doesn't delete anything at shutdown-

Good luck with other methods to accomplish the fix-


http://ubuntuforums.org/forum.php

Did you ever find out what the issue was?

I am having a similar problem.

I have a ramdisk on server1 mounted to a ramdisk on server2.

If server1 goes down (or is rebooted), the server2 mount gets stale and messed up. Cannot unmount it.

The only way I can fix the issue is to edit fsid= in /etc/exports on server1. All I have to do is randomly change the integer value, and re-export. Then, "mount -a" works on server2 ! Weird.

I suspect there is something special about NFS mounting mover ramdisks. Just don't know how to fix. If server1 reboots, I must be able to detect and script a remount.

http://serverfault.com/questions/672...t-a-to-execute