Thanks Erik. Removing the first instance of the print in
/sys/src/9/pc/devether.c appears to fix it:
/* print("soverflow for f->in\n"); */
There is another another print lower down but I left this there for the moment.
term% time upas/fs -f /imaps/imap.gmail.com/address_remo...@gmail.com
!Addi
> Also, I just did a pull from sources which appears to have updated
> almost the complete contents of /386. This caused the "soverflow for
> fx->in" message to appear. I had to run pull three times to get it to
> finish.
maybe my first message wasn't that clear. any ethernet activity
can cause t
On Sat, Jul 24, 2010 at 10:44 PM, Lyndon Nerenberg wrote:
>> what's happening is that the printing of "soverflow for fx->in"
>> is wasting so much time that the imap server gets bored and hangs
>> up.
>
> This is really dragging out for 30 minutes?
No. Not that long.
Also, I just did a pull from
On Mon Oct 26 12:35:07 EDT 2009, andr...@pvv.ntnu.no wrote:
> Our cpu/auth/file went belly up some time during the weekend. It
> responded to ping, but we couldn't drawterm in. No response from
> the vblade process providing storage to our XenServers either.
> Walking down to the machine I found th
Our cpu/auth/file went belly up some time during the weekend. It
responded to ping, but we couldn't drawterm in. No response from
the vblade process providing storage to our XenServers either.
Walking down to the machine I found the screen full of "soverflow
for fx->in" messages. I had to reboot i
