Date: Sun, 06 Dec 2015 03:22:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204813] suggeted improvement for crontab(1)'s newly created files Message-ID: <bug-204813-8-ppiXxlnZ4Z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204813-8@https.bugs.freebsd.org/bugzilla/> References: <bug-204813-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=204813 --- Comment #3 from Mason Loring Bliss <mason@blisses.org> --- Expanding the path would obviate the problem, but it would also change the behaviour for regular users who arguably should have to explicitly add /sbin, /usr/sbin, and similar. I'd be happy with expanding the path. My idea of a default file with a commented out PATH seemed like the least-invasive option - users with established crontabs wouldn't be impacted at all, and new crontabs would have a small, subtle reminder that their PATH isn't necessarily the same as it was in the shell they used to invoke crontab(1). Regardless of whate solution you folks decide is appropriate, thank you for your time and work. -- 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-204813-8-ppiXxlnZ4Z>