Date: Wed, 08 Mar 2006 04:01:30 -0600 From: "F. Even - fbsd-questions" <freebsdlists@elitists.org> To: freebsd-questions@freebsd.org Cc: ringworm01@gmail.com Subject: Re: portmanager core dumps Message-ID: <440EAB7A.4090207@elitists.org>
index | next in thread | raw e-mail
> On Sunday 08 January 2006 18:30, Robert Marella wrote: >> Good Afternoon >> >> At times when in a hurry or not thinking as fast as my fingers, I try >> to run "portupgrade -s | grep OLD" from a regular user account instead >> of "sudo portupgrade -s | grep OLD". > > do you mean "portmanager -s | grep OLD" by any chance? >> >> I would expect portupgrade to insult my intelligence and question my >> heritage .... or is that question my intelligence and insult my >> heritage. Well, it doesn't do either. It core dumps. This will happen >> on more than one system running 6 Stable and the updated portmanager. >> >> [robert@frankie] ~> pkg_info | grep portmanager >> portmanager-0.4.1_4 FreeBSD installed ports status and safe update >> utility >> >> Thanks >> >> Robert > > Portmanager will only run as root, I'll make a note/bug to check error > handling when someone attempts to run it as a normal user. Mike, Please don't disable the ability to run this as a non-root user. I've managed to get it to run by chowning it's config, files under /var/db and the entire ports collection to an update user. Now I can run portmanager -s and it will give me an accurate run-down of what upgrades are needed. I can also then download updates as a restricted user. Changing to root will allow me to update as I need to, and as long as the src is cleaned up, no files owned by root are left behind in the ports tree. This actually works quite nicely. Thanks, Frankhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440EAB7A.4090207>