I encountered the same problem, but used a different solution: make
/var/lib/NetworkManager a symlink to /var/run/NetworkManager (and create
the corresponding directory).
/var/run is a tmpfs filesystem, so it won't generate hard disk wake-ups.
--
You received this bug notification because you
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: network-manager (Ubuntu)
Status: New = Triaged
--
You received this bug notification because
** Changed in: network-manager (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913856
Title:
NetworkManager periodically writes to the disk causing
This bug was fixed in the package network-manager -
0.9.2.0+git201112151936.6b31828-0ubuntu3
---
network-manager (0.9.2.0+git201112151936.6b31828-0ubuntu3) precise; urgency=low
* debian/patches/avoid-periodic-disk-wakeups.patch: avoid waking up disks to
write a timestamp every
strace shows:
open(/var/lib/NetworkManager/timestamps, O_RDONLY) = 20
fstat(20, {st_mode=S_IFREG|0644, st_size=1646, ...}) = 0
read(20, \n[timestamps]\n3c32aa58-a2ed-44e7..., 4096) = 1646
read(20, , 4096) = 0
close(20) = 0
The culprit is periodic_update_active_connection_timestamps() which is
being called every 300 seconds because of:
/* Update timestamps in active connections */
priv-timestamp_update_id = g_timeout_add_seconds (300, (GSourceFunc)
periodic_update_active_connection_timestamps,
** Tags added: battery-power-consumption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913856
Title:
NetworkManager periodically writes to the disk causing wakeups
To manage notifications about
On my system, I only see the singe timestamps file in
/var/lib/NetworkManager. Do you have any active systems connections or
VPNs active at the same time? That would explain the multiple
timestamps files?
From a cursory glance, these timestamps record an active connection's
last-used time so
So, I only see a single timestamps file too, the timestamps.096F6V
filename is probably a short lived temp filename. As for the
configuration, it was a clean install and connected via wireless (and
possibly ethernet).
--
You received this bug notification because you are a member of Ubuntu
This is simple enough, I think we can drop the periodic updates fairly
safely, since the timestamps still get updated when connections go down,
etc. The main goal is that the latest connection should have the highest
timestamp, but I think we already achieve that.
--
You received this bug
10 matches
Mail list logo
