On Wed, 2008-11-26 at 13:31 -0500, Dan Williams wrote: > O > NM will change the hostname just like dhclient-script does, if you have > not set a persistent hostname in /etc/sysconfig/network. If you have > set a persistent hostname in /etc/sysconfig/network, NM will *always* > use that hostname. The hostname was there and listed the whole time, from install (I used askmethod during install so I could get NM to use static, as GUI didn't allow me to). > > It may be the issue where sendmail is happily unaware of network changes > including hostname changes. If, after connecting, you do '/sbin/service > sendmail restart' does that start things working? The real fix here is > to hit stupid services that don't handle network changes in the face > with a nail-studded board, and repeat if they get back up, until they > stop getting up and just lie there. But failing that, forcing them to > restart via a dispatcher script when network changes occur may be the > quickest alternative. No, sendmail wouldn't still send it. I did go to network service and relooked at files (ifcfg-eth0 mainly), saw any differences with NetworkManger and with network. Went back to NM just now and ran epylog cron manually and it got sent. Sooo, it *might* be working now. So maybe something in ifcfg helped and allows it to go now? -- Mike Chambers Fedora Project - Ambassador, Bug Zapper, Tester, User, etc.. mikec302@xxxxxxxxxxxxxxxxx -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
