We'll I had posted a problem regarding diald where it was mysteriously crashing on a daily basis. My solution so I thought was to build SLIP and PPP support directly into the kernel instead of building them as kernel modules. I though that perhaps kerneld was unloading SLIP which diald needs to run. That seemed to help somewhat as diald ran for 23 days before crashing again. There are no errors reported in the syslog and I couldn't find a core file on my system anywhere. My only clue to knowing that diald crashed was I see diald reporting that it removed the stale lockfile on device /dev/ttyS1 which is the device my modem is connected to. At this point I decided to "use the source" and so I've download diald 0.16 as well as the diald patch 0.16.5. I applied the patch to the 0.16 source, compiled the code and temporarily replaced the SuSE 6.0 supplied diald executable This is very frustrating as diald was rock solid in SuSE 5.2 and 5.3. I ran my server for months on end without a reboot and diald was always there. I guess I'll have to look into running diald through init so it will get restarted automatically when it dies if this version I downloaded doesn't have any better stability than the version supplied with SuSE 6.0 Tony -- [EMAIL PROTECTED] -- 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
