Re: portupgrade across NFS
Michael Collette wrote: This problem only occurs when using portupgrade. Both pkg_delete and pkg_deinstall work without error. Also, everything else in the process that portupgrade goes through appears to work properly. Just that /var/db/pkg directory won't delete when NFS mounted. Have you tried the last (2.1.1) version? I've fixed a few problems and one of them looks like yours. But it's not relate to NFS however. -- Dixi. Sem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade across NFS
Sergey Matveychuk wrote: Michael Collette wrote: This problem only occurs when using portupgrade. Both pkg_delete and pkg_deinstall work without error. Also, everything else in the process that portupgrade goes through appears to work properly. Just that /var/db/pkg directory won't delete when NFS mounted. Have you tried the last (2.1.1) version? I've fixed a few problems and one of them looks like yours. But it's not relate to NFS however. No luck. I was back on 2.0.1 which I upgraded with pkg_delete and pkg_add. Still the exact same error with deleting the /var/db/pkg directory. Like I mentioned earlier, we've been going through the source code on this, libraries and all. If you'd like to toss some tweaks for me to test out off list I'd be one very motivated tester here. This glitch may really complicate my network setup here, so doing whatever it takes to fix this is high on my priority list. Just a thought for an ugly hack, but might it be possible to force a check for that directory after it has supposedly been deleted, and if it exists manually delete it? Thanks for getting back with me on this. Going to continue to muck around with things a bit here to see if we can stumble across something that helps. Later on, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade across NFS
Sergey Matveychuk wrote: Michael Collette wrote: No luck. I was back on 2.0.1 which I upgraded with pkg_delete and pkg_add. Still the exact same error with deleting the /var/db/pkg directory. Let's make it clean. You have /var/db/pkg as nfs mounted? You can't remove /var/db/pkg/portname directory? Got one bad bit of information from my previous post. The problem DOES exist when just performing a pkg_deinstall. Apparently the one test I based my earlier post on wasn't repeatable. The problem is not with the portupgrade script itself. Dug in quite a bit further with this today. When pkg_deinstall calls to pkg_delete a .nfs file is created which is showing as being actively accessed by the ruby process. This file vanishes once pkg_deinstall quits. Due to that file, even attempting a rm -rf on that directory will fail within pkg_deinstall. For testing this out, we added a cheap hack to the portupgrade script immediately after the call to pkg_deinstall that just removes the directory once pkg_deinstall has ended. This works, but has no logic or error checking at this point. The pkg_deinstall script does not report that it didn't complete, so the main portupgrade script just keeps on going as though there were no errors. With that being said, what I believe needs to happen in the short term is to have a check within the portupgrade script where if the pkg_deinstall returns successful and the /var/db/pkg directory still exists, delete it. This would be right around line 1721. Obviously the more correct thing to do here would be to correct pkg_deinstall's behavior. That looks like it may be quite a bit more clever to do, thus my recommendation for fixing portupgrade now, and revisit pkg_deinstall later. I'm just concerned that the real problem may have more to do with the ruby engine and NFS than this script, which may take many months to correct. Later on, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade across NFS
I've got a setup here where I need to run portupgrade on a different box from the one where the port is actually going to. I have all the NFS exports setup on the target box and mount points on the installer. Almost everything is working... except the reason for this posting. When portupgrade attempts to remove the entry in /var/db/pkg for the old port, it fails to remove the directory. It does remove all the contents of the directory, but not the directory itself. This problem only occurs when using portupgrade. Both pkg_delete and pkg_deinstall work without error. Also, everything else in the process that portupgrade goes through appears to work properly. Just that /var/db/pkg directory won't delete when NFS mounted. Apparently other folks have had this problem before as I discovered upon googling about. The following PR touches on the matter. http://www.freebsd.org/cgi/query-pr.cgi?pr=32668 Been staring at Ruby code I don't fully understand for the better part of 2 days now, and I don't understand why this glitch is happening. It looks like portupgrade simply calls to pkg_deinstall, which is a wrapper for pkg_delete. Logically if the last 2 work, then portupgrade should as well, but obviously it doesn't. Anyone out there able to make any sense of that Ruby code? Is there something we can patch in there to get this tid bit functional? Thanks, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
