Date: Mon, 03 Apr 2017 14:24:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 48325] [patch] /etc/periodic/security/100.chksetuid doesn't work with spaces in mount points Message-ID: <bug-48325-8-p2jmTrRMVE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-48325-8@https.bugs.freebsd.org/bugzilla/> References: <bug-48325-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=3D48325 aaron@baugher.biz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaron@baugher.biz --- Comment #1 from aaron@baugher.biz --- I came to report this, and found this old bug report. I discovered it on a= ZFS filesystem with a space in the name, which I'd imagine is more common now t= hat it's so easy to create new ZFS filesystems. With a single space in the filesystem name, awk $3 returns a mountpoint of = "on" instead of the correct value. I could parse it out with perl, getting everything between ' on ' and ' ('. That would work for all my filesystems, but I'm not certain it would be universal. Also, is it okay to use perl in= the base system like that, or would it be better to use something like sed? I'= d be glad to make a patch, but I haven't offered a patch for FreeBSD itself befo= re. --=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-48325-8-p2jmTrRMVE>