Port update problem?

[Doug Spangler]

You are correct I meant chapter 4. Just out of curiosity is your INDEX
intact or is that the cause of the odd behavior
of /etc/periodic/weekly/400.status-pkg, portion of the problem. I
understand that it is not the root cause of your problem just a
symptom. 

On Thu, 2010-10-28 at 18:41 +0100, Arthur Chance wrote:
> On 10/28/10 17:56, Doug Spangler wrote:
> > Fetch the current INDEX as well, that happens when there isn't a proper
> > INDEX. Also take a look at the FreeBSD Handbook Chapter 5 and the man
> > page for portsnap
> 
> The command (it's portsnap wrapped up with start & finish time messages 
> that can be run from cron) has worked perfectly correctly for weeks, 
> with no problems. What I'm interested in is why it failed this time when 
> it seemed to behave no differently from any time before, with no error 
> messages.
> 
> BTW, Handbook contents: 5 The X Window System
> 
> Methinks you mean Chapter 4, which I'm familiar with, ditto portsnap. I 
> switched to using it rather than csup months ago, and it's been 
> faultless until now. I probably should have copied cperciva on the 
> initial post.
>