Commit 3167c612 authored by Allison Karlitskaya's avatar Allison Karlitskaya

Deprecate g_unix_mount_monitor_set_rate_limit()

Deprecate g_unix_mount_monitor_set_rate_limit() and turn it into a

This function doesn't behave as advertised.  It only controls rate
limiting for filesystem-based monitors.  It has no impact over reporting
mount changes on Linux, for example, because those are based on polling
for changes in /proc (which doesn't use filesystem monitors).  It also
has no impact on Mac OS because a library interface is used there.

This was added in in
order to be used by HAL, which is effectively dead.  udisks no longer
uses this code at all.
parent 73d4e6f1
......@@ -1495,22 +1495,22 @@ g_unix_mount_monitor_init (GUnixMountMonitor *monitor)
* @limit_msec: a integer with the limit in milliseconds to
* poll for changes.
* Sets the rate limit to which the @mount_monitor will report
* consecutive change events to the mount and mount point entry files.
* This function does nothing.
* Before 2.44, this was a partially-effective way of controlling the
* rate at which events would be reported under some uncommon
* circumstances. Since @mount_monitor is a singleton, it also meant
* that calling this function would have side effects for other users of
* the monitor.
* Since: 2.18
* Deprecated:2.44:This function does nothing. Don't call it.
g_unix_mount_monitor_set_rate_limit (GUnixMountMonitor *mount_monitor,
gint limit_msec)
g_return_if_fail (G_IS_UNIX_MOUNT_MONITOR (mount_monitor));
if (mount_monitor->fstab_monitor != NULL)
g_file_monitor_set_rate_limit (mount_monitor->fstab_monitor, limit_msec);
if (mount_monitor->mtab_monitor != NULL)
g_file_monitor_set_rate_limit (mount_monitor->mtab_monitor, limit_msec);
......@@ -130,7 +130,7 @@ GLIB_AVAILABLE_IN_2_44
GUnixMountMonitor *g_unix_mount_monitor_get (void);
GUnixMountMonitor *g_unix_mount_monitor_new (void);
void g_unix_mount_monitor_set_rate_limit (GUnixMountMonitor *mount_monitor,
int limit_msec);
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment