On Mon, 2 May 2016 11:28-0600, Alan Somers wrote:
> "-q" is only really intended for embedded systems that don't use the
> standard syslogd or that are extremely concerned about syslogd's pipe
> bandwidth and/or CPU usage. Most people should control devd's chattiness
> with /etc/syslog.conf. Thi
"-q" is only really intended for embedded systems that don't use the
standard syslogd or that are extremely concerned about syslogd's pipe
bandwidth and/or CPU usage. Most people should control devd's chattiness
with /etc/syslog.conf. This setting is good for most people. It will log
actions dev
> On May 1, 2016, at 9:07 AM, Trond Endrestøl
> wrote:
>
> On Wed, 27 Apr 2016 13:46-0400, Scott Long wrote:
>
>> Thanks for the report. I might be mistaken, but the default system
>> is not configured to direct devd messages to user.info, so I didn’t
>> see this during my development. How
On Wed, 27 Apr 2016 13:46-0400, Scott Long wrote:
> Thanks for the report. I might be mistaken, but the default system
> is not configured to direct devd messages to user.info, so I didn’t
> see this during my development. However, what you’re reporting is
> definitely annoying, so Warner Los
Hi Trond,
Thanks for the report. I might be mistaken, but the default system is not
configured to direct devd messages to user.info, so I didn’t see this during my
development. However, what you’re reporting is definitely annoying, so Warner
Losh and I are working on a solution.
Scott
> On
Hi,
The symptoms began after upgrading from stable/10 r298033 to stable/10 r298573.
Apr 27 18:40:00 [HOSTNAME] devd: Processing event '!system=CAM
subsystem=periph type=error device=cd0 serial="R8KL6GKC900AFG"
cam_status="0xcc" scsi_status=2 scsi_sense="70 02 04 01" CDB="00 00 00 00 00 00
" '
