1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204
//! Code to watch configuration files for any changes.
use std::collections::HashSet;
use std::path::{Path, PathBuf};
use std::sync::mpsc::channel as std_channel;
use std::time::Duration;
use arti_client::config::Reconfigure;
use arti_client::TorClient;
use notify::Watcher;
use tor_config::ConfigurationSources;
use tor_rtcompat::Runtime;
use tracing::{debug, info, warn};
use crate::{ArtiCombinedConfig, ArtiConfig};
/// How long (worst case) should we take to learn about configuration changes?
const POLL_INTERVAL: Duration = Duration::from_secs(10);
/// Launch a thread to watch our configuration files.
///
/// Whenever one or more files in `files` changes, try to reload our
/// configuration from them and tell TorClient about it.
pub fn watch_for_config_changes<R: Runtime>(
sources: ConfigurationSources,
original: ArtiConfig,
client: TorClient<R>,
) -> anyhow::Result<()> {
let (tx, rx) = std_channel();
let mut watcher = FileWatcher::new(tx, POLL_INTERVAL)?;
for file in sources.files() {
watcher.watch_file(file)?;
}
std::thread::spawn(move || {
// TODO: If someday we make this facility available outside of the
// `arti` application, we probably don't want to have this thread own
// the FileWatcher.
debug!("Waiting for FS events");
while let Ok(event) = rx.recv() {
if !watcher.event_matched(&event) {
// NOTE: Sadly, it's not safe to log in this case. If the user
// has put a configuration file and a logfile in the same
// directory, logging about discarded events will make us log
// every time we log, and fill up the filesystem.
continue;
}
while let Ok(_ignore) = rx.try_recv() {
// Discard other events, so that we only reload once.
//
// We can afford to treat both error cases from try_recv [Empty
// and Disconnected] as meaning that we've discarded other
// events: if we're disconnected, we'll notice it when we next
// call recv() in the outer loop.
}
debug!("FS event {:?}: reloading configuration.", event);
match reconfigure(&sources, &original, &client) {
Ok(exit) => {
info!("Successfully reloaded configuration.");
if exit {
break;
}
}
Err(e) => warn!("Couldn't reload configuration: {}", e),
}
}
debug!("Thread exiting");
});
// Dropping the thread handle here means that we don't get any special
// notification about a panic. TODO: We should change that at some point in
// the future.
Ok(())
}
/// Reload the configuration files, apply the runtime configuration, and
/// reconfigure the client as much as we can.
///
/// Return true if we should stop watching for configuration changes.
fn reconfigure<R: Runtime>(
sources: &ConfigurationSources,
original: &ArtiConfig,
client: &TorClient<R>,
) -> anyhow::Result<bool> {
let config = sources.load()?;
let (config, client_config) = tor_config::resolve::<ArtiCombinedConfig>(config)?;
if config.proxy() != original.proxy() {
warn!("Can't (yet) reconfigure proxy settings while arti is running.");
}
if config.logging() != original.logging() {
warn!("Can't (yet) reconfigure logging settings while arti is running.");
}
client.reconfigure(&client_config, Reconfigure::WarnOnFailures)?;
if !config.application().watch_configuration {
// Stop watching for configuration changes.
return Ok(true);
}
Ok(false)
}
/// A wrapper around `notify::RecommendedWatcher` to watch a set of parent
/// directories in order to learn about changes in some specific files that they
/// contain.
///
/// The `Watcher` implementation in `notify` has a weakness: it gives sensible
/// results when you're watching directories, but if you start watching
/// non-directory files, it won't notice when those files get replaced. That's
/// a problem for users who want to change their configuration atomically by
/// making new files and then moving them into place over the old ones.
///
/// For more background on the issues with `notify`, see
/// <https://github.com/notify-rs/notify/issues/165> and
/// <https://github.com/notify-rs/notify/pull/166>.
///
/// TODO: Someday we might want to make this code exported someplace. If we do,
/// we should test it, and improve its API a lot. Right now, the caller needs
/// to mess around with `std::sync::mpsc` and filter out the events they want
/// using `FileWatcher::event_matched`.
struct FileWatcher {
/// An underlying `notify` watcher that tells us about directory changes.
watcher: notify::RecommendedWatcher,
/// The list of directories that we're currently watching.
watching_dirs: HashSet<PathBuf>,
/// The list of files we actually care about.
watching_files: HashSet<PathBuf>,
}
impl FileWatcher {
/// Like `notify::watcher`, but create a FileWatcher instead.
fn new(
tx: std::sync::mpsc::Sender<notify::DebouncedEvent>,
interval: Duration,
) -> anyhow::Result<Self> {
let watcher = notify::watcher(tx, interval)?;
Ok(Self {
watcher,
watching_dirs: HashSet::new(),
watching_files: HashSet::new(),
})
}
/// Watch a single file (not a directory). Does nothing if we're already watching that file.
fn watch_file<P: AsRef<Path>>(&mut self, path: P) -> anyhow::Result<()> {
// Make the path absolute (without necessarily making it canonical).
//
// We do this because `notify` reports all of its events in terms of
// absolute paths, so if we were to tell it to watch a directory by its
// relative path, we'd get reports about the absolute paths of the files
// in that directory.
let cwd = std::env::current_dir()?;
let path = cwd.join(path.as_ref());
debug_assert!(path.is_absolute());
// See what directory we should watch in order to watch this file.
let watch_target = match path.parent() {
// The file has a parent, so watch that.
Some(parent) => parent,
// The file has no parent. Given that it's absolute, that means
// that we're looking at the root directory. There's nowhere to go
// "up" from there.
None => path.as_ref(),
};
// Start watching this directory, if we're not already watching it.
if !self.watching_dirs.contains(watch_target) {
self.watcher
.watch(watch_target, notify::RecursiveMode::NonRecursive)?;
self.watching_dirs.insert(watch_target.into());
}
// Note this file as one that we're watching, so that we can see changes
// to it later on.
self.watching_files.insert(path);
Ok(())
}
/// Return true if the provided event describes a change affecting one of
/// the files that we care about.
fn event_matched(&self, event: ¬ify::DebouncedEvent) -> bool {
let watching = |f| self.watching_files.contains(f);
match event {
notify::DebouncedEvent::NoticeWrite(f) => watching(f),
notify::DebouncedEvent::NoticeRemove(f) => watching(f),
notify::DebouncedEvent::Create(f) => watching(f),
notify::DebouncedEvent::Write(f) => watching(f),
notify::DebouncedEvent::Chmod(f) => watching(f),
notify::DebouncedEvent::Remove(f) => watching(f),
notify::DebouncedEvent::Rename(f1, f2) => watching(f1) || watching(f2),
notify::DebouncedEvent::Rescan => {
// We've missed some events: no choice but to reload.
true
}
notify::DebouncedEvent::Error(_, Some(f)) => watching(f),
notify::DebouncedEvent::Error(_, _) => false,
}
}
}