Re: Portupgrade killed everytime

2004-08-27 Thread James Brown
Try running it using strace, such as "strace portupgrade vim" and see what it's doing. I checked my kernel and found the PROCFS and PSUEDOFS options were in there. I have added this line to my fstab: "proc/procprocfs rw00" I no longer see this message: # strace portupgrade vim str

Re: Portupgrade killed everytime

2004-08-25 Thread James Brown
Adam Smith wrote: Try running it using strace, such as "strace portupgrade vim" and see what it's doing. Sorry I didn't get a chance to reply yesterday. I now have the strace port installed but have hit a small problem (as mentioned by Joshua Tinnin). I'm not familiar with strace either and is th

Re: Portupgrade killed everytime

2004-08-23 Thread Joshua Tinnin
On Monday 23 August 2004 04:25 pm, Adam Smith <[EMAIL PROTECTED]> wrote: > On Tue, Aug 24, 2004 at 12:21:09AM +0100, James Brown said: > > Whenever I run portupgrade, I wait about 30 seconds only to see it die: > > > > # portupgrade clamav > > Killed > > # portupgrade vim > > Killed > > Try running

Re: Portupgrade killed everytime

2004-08-23 Thread Steven Friedrich
In /usr/ports/UPDATING, there is a note about upgrading from an older version of Ruby to the latest. Have you been reading UPDATING? You might want to try what's there for this problem before you spend a lot of time troubleshooting... On Monday 23 August 2004 07:21 pm, James Brown wrote: > Wh

Re: Portupgrade killed everytime

2004-08-23 Thread Adam Smith
On Tue, Aug 24, 2004 at 12:21:09AM +0100, James Brown said: > Whenever I run portupgrade, I wait about 30 seconds only to see it die: > > # portupgrade clamav > Killed > # portupgrade vim > Killed Try running it using strace, such as "strace portupgrade vim" and see what it's doing. -- Adam Sm

Portupgrade killed everytime

2004-08-23 Thread James Brown
Whenever I run portupgrade, I wait about 30 seconds only to see it die: # portupgrade clamav Killed # portupgrade vim Killed I have a recent cvsup of 'ports-all' on 5.2.1-RELEASE-p9 and have run 'make index' and 'pkgdb -F'. Someone at bsdforums.org has kindly suggested that I'm seeing a Ruby probl