I noticed very recently that diald was dying for no apparent reason on my server. I found it strange since I've been using diald since I first started using SuSE Linux 5.2. My server system that diald runs on is up for months at a time and only goes down for a kernel patch or SuSE upgrade. Less than two weeks ago I upgraded my server to SuSE 6.0 and about a week after the upgrade I noticed that diald was dying every day. I'm not sure what was going as there were no error messages in the syslog file and I couldn't find a core file anywhere on my system. The only thing I could come up with is that perhaps the SLIP module was being unloaded from the system. I know that diald needs SLIP and so the only thing I could think of as a possible solution was to build SLIP directly into the kernel rather than making it a module. So far diald has been running for more than 24 hours. That is encouraging since before I reconfigured and recompiled my server's kernel, diald didn't seem to be able to run more than 12 hours before dying. I would have to restart it in the morning for my daily email check as it seemed to die sometime in the middle of the night. Can anyone else shed some light on this problem? Tony -- Tony Schlemmer mailto:[EMAIL PROTECTED] http://www.sequeltech.com -- To get out of this list, please send email to [EMAIL PROTECTED] with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
