On 6 July 2015 at 10:45, Linux4Bene <linux4b...@telenet.be> wrote: > Op Sun, 05 Jul 2015 17:32:56 -0300, schreef Beco: > > > > # apt-get remove wpasupplicant > > > > I could break the "while" loop deleting syslog. It stoped spamming. > > Looks like all messages was linked to it. > > > > I don't know very much wpasupplicant. Ill this software be needed in the > > near future? > > Only if you plan on using wireless on your server (which seems weird) so > probably not. > > > Im afraid the system is working only now, and will be unreachable next > > reboot. > Then plan a scheduled maintenance where the users know the system won't > be available for a while. Make sure you have backups of the system. > Notify the users, shutdown the system, disable wireless in the BIOS, > then reboot and fix whatever is on your path. > You might want to do this on premise and have a system at hand connected > to the net to search for info if you do encounter a problem. > > Regards > > Hi Bene,
Well, with you I think its 3 suggestions to disable wireless via BIOS. So, I've just changed my mind and I'll disable it. What is the point of asking for suggestions and no following them? If I need it one day, I'll re-enable. Thanks for the tip and for the agenda. Cheers, Beco. -- Dr Beco A.I. researcher "I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant" -- Alan Greenspan GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A Creation date: pgp.mit.edu ID as of 2014-11-09
