From owner-freebsd-bugs@freebsd.org Sun Dec 6 03:22:37 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2432A3B267 for ; Sun, 6 Dec 2015 03:22:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6FA61EE1 for ; Sun, 6 Dec 2015 03:22:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tB63Mbha065935 for ; Sun, 6 Dec 2015 03:22:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204813] suggeted improvement for crontab(1)'s newly created files Date: Sun, 06 Dec 2015 03:22:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mason@blisses.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Dec 2015 03:22:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204813 --- Comment #3 from Mason Loring Bliss --- 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.