Hi all, Thanks for the thoughts!
On 02/04/2008, Rod Whitby <[EMAIL PROTECTED]> wrote: > Giles, it looks like you're really going to need a serial console to debug this one ... What would I look for with a serial console? I assume that would give me the console output and persist over a reboot, so perhaps I'm looking for kernel panic messages or the like? If so, I assume (as per < http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort>) that I'll need to start doing a bit of hardware hacking to enable the internal serial port, is that right? Regards, Giles On 02/04/2008, Rod Whitby <[EMAIL PROTECTED]> wrote: > > Bob Cox wrote: > > > Giles Thomas <[EMAIL PROTECTED]> wrote: > > > > > There's nothing immediately obvious in the logfiles in /var/log; I've > > > looked > > > at messages, syslog, kern.log and debug. Is there anywhere else I > > > should be > > > looking for clues about why this is happening? > > > > > > > There may be a separate samba log folder containing the samba daemon > > logfile: /var/log/samba/log.smbd > > > > It's unlikely that samba could cause the slug to reboot. But I guess > anything is possible in weird cases like this. > > Giles, it looks like you're really going to need a serial console to debug > this one ... > > -- Rod > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > -- Giles Thomas [EMAIL PROTECTED]
