I had this a while ago. Used to happen after resume from suspend on my ThinkPad. Maybe logrotate is worth a look:-
http://linux.die.net/man/8/logrotate

Blacklist mei and mei-me ...

hernanmedellin thanks

i have limitated skills. Can you give me a how to guide?

-i did rmmod mei_me according to genss but syslog keep increasing (a much short frequency of course, instead mb to gb, kb to mb), almost i post the SOLVED mark on my treads but i want to delete this problem eternaly.

thanks genns to.

Here is one , in Spanish , you can translate it into your language ...

https://ecoslackware.wordpress.com/2...de-suspension/

Saludos ...

hernanmedellin thanks again. But, that post its related about suspension and after ram. I will follow that instructions according to the refering link. Today my syslog breaks again my system, 100 gb again on my disk, i was working as ussuall even not using VB, just working on libreoffice, by the way, i lost my file after fix temporary the problem, (without suspension, hibernate or whatever). Lets see whats happen after this https://ecoslackware.wordpress.com/2...de-suspension/

i dont want to say this but, and this is the last post that i follow, this syslog issue cant be tolerable anymore, its breaks your computer, if someone ask me if slackware has malware i perfectly say yes, its call syslog. My friend had to trash his laptop because of that, he went to cinema and back to home he just works and rescue in 15 minutes some personal info, the problem was the syslog mei curst, he had to put some gloves to manage the keybord because of heat. He still waiting to linus torvals or someone else to claim a new laptop.

i want to thanks everyone for help.

Did you even read this? I am fluent in Spanish but have not practiced in many years. I am out of practice, but just glancing at the article I can confirm that this is exactly what you are looking for- a tutorial....

This is the most outrageous thing I've seen posted on LinuxQuestions.org in quite some time. Although... I do have the LQ Newbie forum ignored.

mralk3, did you mine?. This is the most ridiculous issue (but dangerous) that i ever seen on slackware. Lets me see, im just creating and makings hokes, i post this on linuxquestions just for fun. Yeah rigth a noob guy.

In any case, Intel is the culprit, not Slackware ...

I apologize for being so harsh. There are several provided solutions to your problem. This is not an issue caused by Slackware. Syslog is not malware. Nothing about this is dangerous.

Apply the solutions provided and everything will be ok!

allenlinux, syslog is doing exactly what it is supposed to do. It is storing the messages sent to it by programs/modules. If a program/module is spamming the syslog, that is the program/modules fault, not syslog. syslog just records it like it is supposed to do.

If you are unable/unwilling to try to deal with the program/modules that are spamming the syslog, have you tried the solution VisionIncision suggested about using logrotate? That can rotate a log when it reaches a certain size and then remove old logs after a certain number have been rotated. While this won't solve your spamming, it certainly will prevent syslog from filling up your / partition. Have a look at this stackoverflow question on some ideas for setting up logrotate based on size.

Another option is to create a separate partition for /var or /var/log. It wouldn't solve the problem of it filling the partition, but it would cause other partitions to remain unaffected. But I'm not sure if a full partition where the logs are stored can cause problems. At least /tmp and /home would still be writeable for the files they need to create...

This is what I do and I have found it to always be a good idea.

by this time i solve with this

0.- cd /var/log/

rm -rf messages.1

rm -rf messages.2

rm -rf messages.3

rm -rf messages.4

rm -rf syslog

rm -rf syslog.1

rm -rf syslog.2

1.- rmmod mei_me

2.- ls -l /lib/modules/3.10.17/kernel/drivers/misc/mei | grep mei

3.- nano /etc/modprobe.d/blacklist.conf

blacklist mei
blacklist mei-me

4.- reboot


Thanks to everyone.