https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/2966091#M119427 From the man page:<BR /><BR />"If the - argument is<BR /> specified, dmesg computes (incrementally) the new messages since the<BR /> last time it was run and places these on the standard output. This is<BR /> typically used with cron (see cron(1)) to produce the error log<BR /> /var/adm/messages by running the command:<BR /><BR /> /usr/sbin/dmesg - &gt;&gt; /var/adm/messages<BR /><BR /> every 10 minutes."<BR /><BR /><BR />You could adapt this technique to filter out the unwanted messages (with "grep -v") and check the /var/adm/messages file rather then dmesg itself.<BR /><BR /><BR />Pete Mon, 05 May 2003 18:25:49 GMT Pete Randall 2003-05-05T18:25:49Z https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/2966090#M119426 Is there a way for dmesg to ignore certain messages ??<BR /><BR />I have some database file systems that are always 100% full, and dmesg keeps recording the problem, which I don't care about ....<BR /><BR />Thanks<BR /> Mon, 05 May 2003 18:18:47 GMT https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/2966090#M119426 MikeL_4 2003-05-05T18:18:47Z https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/2966091#M119427 From the man page:<BR /><BR />"If the - argument is<BR /> specified, dmesg computes (incrementally) the new messages since the<BR /> last time it was run and places these on the standard output. This is<BR /> typically used with cron (see cron(1)) to produce the error log<BR /> /var/adm/messages by running the command:<BR /><BR /> /usr/sbin/dmesg - &gt;&gt; /var/adm/messages<BR /><BR /> every 10 minutes."<BR /><BR /><BR />You could adapt this technique to filter out the unwanted messages (with "grep -v") and check the /var/adm/messages file rather then dmesg itself.<BR /><BR /><BR />Pete Mon, 05 May 2003 18:25:49 GMT https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/2966091#M119427 Pete Randall 2003-05-05T18:25:49Z