[Pkg-utopia-maintainers] Bug#755477: network-manager: fills up /var/log/partition

[Merlini Adrien]

On 05/08/2014 00:38, Tomas Janousek wrote:
> Hi,
>
> On Mon, Jul 21, 2014 at 05:54:58PM +0900, Merlini Adrien wrote:
>> I have just upgraded network-manager to 0.9.10. Since the upgrade when
>> activating the hotspot/shared AP feature, network-manager will 'spam'
>> /var/log/deamon.log with the message provided bellow. This ends up filling
>> up completly the partition containing /var/log and preventing parts of the
>> system from running. The filling up is also relatively fast, it took a few
>> minutes to reach 2GB on a laptop HDD.
>>
>> I am not sure what causes the original issue, I will investigate this later.
>>
>> [...]
>>
>> Regarding the original issue could it be caused by the fact that the
>> name of the computer and the SSID of the hotspot are the same ('yuno')?
>> This would explain the "Name not unique on network" part of the logs.
> Any progress in investigating the issue?  I hit this a few weeks ago
> immediately after upgrading network-manager even without activating a hotspot
> as I keep a monitor interface around for aircrack-ng purposes.  Today, I hit
> it again when activating a hotspot.  It does seem quite silly that
> network-manager tries to manage a monitor interface it itself creates for the
> hotspot, and doubly so that it fills the logs complaining about it.  You're
> lucky that you keep a separate partition just for /var/log. :-)
>
> Anyway, the workaround I use is this in
> /etc/NetworkManager/NetworkManager.conf:
>
> [keyfile]
> unmanaged-devices=interface-name:wlan1mon0;interface-name:mon.wlan1
>
> (wlan1mon0 is the monitor interface that I created, mon.wlan1 is the one
> network-manager creates itself)
>
Hi,

not really, i was hopping for an update... but nothing so far. However
I've just updated network-manager on another computer with a completely
different hardware, and the exact same issue occurred :/
So given that it happens on three different platform, I'd say that
something is wrong with network-manager...

I tried your fix and it worked for me, replacing wlan1 by wlan0 (iface
created by network-manager for me). Thanks a lot for sharing this.

I couldn't find any reference to this issue on google though. Are we the
only two pple affected :o? The fix you used isn't really trivial...

Thanks again for sharing the fix,

Regards