Actually I spoke too soon. When I watch my FR boot, I can see the wpa_supplicant is printing out some errors and a fair amount of text as to what the error is. When I do a "dmesg" those messages are not there, when I do a logread to a file and examine the file, it's not their either. Also, logread is the output from the driver and kernel printk primitive, not what I would see in a proper syslog which is where wpa_supplicant and various startup daemons would print.
Cheers!! On Thu, Jan 22, 2009 at 2:58 PM, john dowd <jdowds...@gmail.com> wrote: > yes it does, thanks! > > On Thu, Jan 22, 2009 at 2:53 PM, Marcel <tan...@googlemail.com> wrote: >> Am Thursday 22 January 2009 20:48:43 schrieb john dowd: >>> I see the syslog.conf file says to put the messages in >>> /var/log/messages but there is no file and no logged output. I really >>> need to see the log from when the system was booting. syslogd-ng is >>> actually running so where is its output? >>> >>> Cheers!! >> >> Doesn't logread show the syslog? IIRC it does.... Correct me if I'm wrong. :) >> >> -- >> Marcel >> >> _______________________________________________ >> Openmoko community mailing list >> email@example.com >> http://lists.openmoko.org/mailman/listinfo/community >> > > > > -- > John Dowd > > 133 Waverley St. > Ottawa Ont. K2P 0V3 > Home: (613)234-7884 > Cell: (613)316-7884 > email: jdowdster at gmail dot com > -- John Dowd 133 Waverley St. Ottawa Ont. K2P 0V3 Home: (613)234-7884 Cell: (613)316-7884 email: jdowdster at gmail dot com _______________________________________________ Openmoko community mailing list firstname.lastname@example.org http://lists.openmoko.org/mailman/listinfo/community