Dmesg and error logs.

From: Joshua Lewis (jmlewis_at_dslextreme.com)
Date: 09/11/04

  • Next message: michael johnson: "Re: Dmesg and error logs." 
    Date: Fri, 10 Sep 2004 17:00:22 -0700 (PDT)
To: freebsd-newbies@freebsd.org

    I am trying to troubleshoot an e-mail issue and was wondering if anyone
    can give me some info on errors and where to find them. Specifically:

    What log file does dmesg read from?

    Will dmesg give me any DNS errors or Postfix errors?

    If not what error log should I be looking at?

    Thanks in advanced for any help.

    Thank you,
    Joshua Lewis

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"

  • Next message: michael johnson: "Re: Dmesg and error logs."

    Relevant Pages

    • Re: Dmesg and error logs.
      ... michael johnson wrote: ... >> What log file does dmesg read from ... >> Will dmesg give me any DNS errors or Postfix errors? ... /etc/syslog.conf regarding the writing of console output ...
      (freebsd-newbies)
    • Re: 2.6.26-rc1 regression since 2.6.25
      ... On Mon, 12 May 2008, Lukas Hejtmanek wrote: ... log file for that? ... use a kernel that has CONFIG_USB_DEBUG turned on. ... The dmesg is attached to the bug: ...
      (Linux-Kernel)
    • Exchange SMTP logs time stamp?
      ... I am trying to troubleshoot a problem with SMTP and have the logging ... If I open up the last log file it has time stamps which are 1 hour behind?, ...
      (microsoft.public.exchange.admin)
    • Re: KB920685 wont install
      ... Find the log file ...and can you post it here? ... Robert wrote: ... I have no idea how to troubleshoot this to get it installed. ... Error Code: 0x8007F01E ...
      (microsoft.public.windows.server.sbs)
    • Re: 2.6.26-rc1 regression since 2.6.25
      ... log file for that? ... use a kernel that has CONFIG_USB_DEBUG turned on. ... The dmesg is attached to the bug: ...
      (Linux-Kernel)