Date: Mon, 29 Jan 2018 12:06:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224015] filemon(4) can't deal with newlines in paths Message-ID: <bug-224015-8-N4uMMQftZ3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224015-8@https.bugs.freebsd.org/bugzilla/> References: <bug-224015-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224015 --- Comment #4 from Jan Bramkamp <crest@bultmann.eu> --- The problem isn't that make's meta mode doesn't work for sane code bases, b= ut that filemon could be very useful for dealing with other kinds of applicati= ons as well. Those applications have to support all user provided file names. Y= es a user should be smacked over the head for creating file names with new lines, but that isn't valid excuse leave APIs broken. In theory a path can contain= all characters except the NUL byte which acts as terminator for C strings. And = the forward slash is the only path separator. A file system monitoring API shou= ld be able to deal with all legal paths not just some "sane" subset we all like because it lets us get away with sloppy scripts (e.g. assume that file names don't include anything from $IFS, will neither contain neither backticks nor dollar signs, ...). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224015-8-N4uMMQftZ3>