 Binderdev Messages, how to remove them? |
OESF Portables Forum > Everything Else > Archived Forums > Distros, Development, and Model Specific Forums > Zaurus Distro Support and Discussion > Android  |
 Jan 19 2008, 05:47 AM
Post
#1
|
|
 Group: Members Posts: 1,014 Joined: 15-February 05 From: France Member No.: 6,477  |
when you switch from android to a console , there are a lot of binder_open / binder_release messages.
how can we suppress them ? i tried to launch init with 2> /dev/null with no luck... |
 |
 
|
|
Jan 22 2008, 07:27 PM
Post
#2
|
|
|
Group: Members Posts: 45 Joined: 30-December 07 From: Japan Member No.: 21,136 |
QUOTE(jpmatrix @ Jan 19 2008, 10:47 PM)  when you switch from android to a console , there are a lot of binder_open / binder_release messages. how can we suppress them ? i tried to launch init with 2> /dev/null with no luck... binderdev.ko outputs those messages using printk(KERN_WARING). If they annoy you, modify /etc/init.d/syslog manually. line 50 start-stop-daemon -S -b -n klogd -a /sbin/klogd -- -n Add loglevel, say 4 (KERN_NOTICE). Any number less than 5 (KERN_WARNING) suppresses them. start-stop-daemon -S -b -n klogd -a /sbin/klogd -- -n -c 4 After save the file, restart syslogs and kernlogd /etc/init.d/syslog restart I'm not sure how Debian confiures syslogd/kernlogd, but as long as it uses busybox version, this way could work. Cheers, |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 25th April 2018 - 04:15 PM |