On Tue, Mar 24, 2009 at 10:27 AM, mabshoff <[email protected]> wrote: > > > > On Mar 24, 1:27 am, William Stein <[email protected]> wrote: >> On Mon, Mar 23, 2009 at 3:39 PM, mabshoff <[email protected]> wrote: > > <SNIP> > >> I temporarily put a few ip's into /etc/resolv.conf until I can restart >> the vmware server safely (i.e., I'm onsite), and according to >> >> http://groups.google.com/group/sage-trac >> >> it looks like trac notifications are now working again. > > Yep, it is working for me again. > >> I'll restart all the vmware stuff tomorrow (=Wednesday) when I drop by >> campus and that should fix whatever this nameserver issue is. > > Cool.
Prompted by Gonzalo's email, I looked into this again. I restarted the vmware natd daemon, and now everything is working fine again on all the vmware machines. Since this problem occurred exactly once in 4 months of heavy usage, I don't think it warrants changing the entire DNS setup of all the virtual machines yet. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
