Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
go away (dunno really how, this time the pppoeconf internet connection didnt stop working after reboot).
now i have a "problem", if im not using a GUI, i noticed there were WIERD messages flooding my screen, messages that are logged in 2 diferent files, and im attaching both as examples (with just a few messages, both files were 16++ mb in size, and rapidly growing)
the more ETH* interfaces i have enabled, the more messages appear, and more frequently.
Any idea why i get those ? how to fix the reason for they to appear, or at least, to prevent them from appearing ?
Without having looked at these "weird" messages, I'd venture a guess that your syslogger is configured to log some/all messages to the console, in addition to logging them to the messages.log and kernel.log files.
Examine your syslog.conf file to see what's being logged where, and adjust accordingly.
Then, restart syslogd.
I believe there's another setting also, in the kernel, which can be controlled via the kernel boot line and maybe other means, which tells the kernel what device to use as the default console. If adjusting your syslogger hasn't solved your issue to your liking, then hopefully by the time you need further help, someone will have provided a bit more info about this 'other setting' to which I refer.
for now i commented the lines in rsyslog.conf that mentioned the files that were used for loggin this stuff (syslog, kern.log and messages)
And did that stop the stuff going onto the console?
If so....
Quote:
but this prevents loggin of some other stuff.
...then you need to break up the sections of the syslog.conf file, and log individual items to where you want them to go. Or edit the file such that nothing gets logged to consoles, only to files.
i dont know about the console, i was able to confirm that the files stoped getting the messages, but i had to leave and was unable to do anymore, until later today that i get back home again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.