On Tue, May 24, 2016 at 10:58:45AM +0200, Jeremie Courreges-Anglas wrote: > Artturi Alm <[email protected]> writes: > > >>Synopsis: dmesg spam > >>Category: user amd64 > >>Environment: > > System : OpenBSD 6.0 > > Details : OpenBSD 6.0-beta (GENERIC.MP) #2111: Mon May 23 00:15:10 > > MDT 2016 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > >>Description: > > i get useless ugly irritating spam on console. > > liek: > > chrome(6007): mmap: mandatory W^X > > chrome(83796): mmap: mandatory W^X > > chrome(19957): mmap: mandatory W^X > > firefox(74606): mmap: mandatory W^X > > chrome(6007): mmap: mandatory W^X > > chrome(50373): mmap: mandatory W^X > > It may be useless for you, but it is currently useful for developers. > Did you consider ignoring it?
And i did try even, and im not against the message itself, i understand it is a positive thing, but imho it does need some kind of a ratelimit, maybe once per process (or better yet; a knob for turning it off). I'm a user who does almost constantly switch different usb devices attached to my workstation while hacking, and these messages keep coming up on the background with no user interaction what so ever, so i either need to focus checking the console immediately after plugging in, or like whole of last night due this new feature fckng up on my habbits: grep or scroll dmesg manually every time.. Obviously, if there was something on cvs to send a diff against, i wouldn't have resorted to patching w/dd.. -Artturi/dontwantitinmyface > > -- > jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
