In file /usr/src/linux/include/linux/kernel.h there is the define for KERN_ALERT :- #define KERN_ALERT "<1>" /* action must be taken immediately */ As you can see that KERN_ALERT is having value 1 and generally the "console_loglevel" (i.e. the first value of "/proc/sys/kernel/printk") is 1 and thas why it doesn't print all the printk messages which you try to print with <KERN_ALERT>... Because it is the rule that "Messages with a higher priority than this will be printed to the console". Just read "/usr/src/linux/Documentation/filesystems/proc.txt"'s printk section for more details. The work around to the problem is, just run the following command :- $ echo 8 > /proc/sys/kernel/printk This thing will cause messages from all the levels to go to the console... Hope this helps... Thanks. Sumit Sharma. On Wed, 30 Jun 2004 so usp wrote : >Hi, > >Im implementing a syscall and I want to write some >information on the user terminal. Ive heard that >using printk(KERN_ALERT"String") could return "String" >to the terminal, but it doesnt. It just modifies the >file /var/log/messages. My distribution is Fedora Core >2 (kernel 2.6.5). Did somebody get the same problem? >Did I do something wrong? The syscall is working >perfectly, the only problem is that I want to return >information to the user, and using the copy_to_user >function isnt appropriate, once there are lots of >information (more than 5) I want to retrieve, with >different types (not only string). > >Thanks > > > >______________________________________________________________________ > >Yahoo! Mail - agora com 100MB de espa�, anti-spam e antiv�us gr�is! >http://br.info.mail.yahoo.com/ > >-- >Kernelnewbies: Help each other learn about the Linux kernel. >Archive: http://mail.nl.linux.org/kernelnewbies/ >FAQ: http://kernelnewbies.org/faq/ >
