From owner-freebsd-bugs@FreeBSD.ORG  Sun Feb 15 23:23:32 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CEE068A6
 for <freebsd-bugs@FreeBSD.org>; Sun, 15 Feb 2015 23:23:32 +0000 (UTC)
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 B3DA46C2
 for <freebsd-bugs@FreeBSD.org>; Sun, 15 Feb 2015 23:23:32 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1FNNWWk072338
 for <freebsd-bugs@FreeBSD.org>; Sun, 15 Feb 2015 23:23:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 197567] chflags -f argument ignored when no file found to be
 modified
Date: Sun, 15 Feb 2015 23:23:32 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jilles@FreeBSD.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: cc
Message-ID: <bug-197567-8-dqRQFNqUwn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-197567-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-197567-8@https.bugs.freebsd.org/bugzilla/>
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Feb 2015 23:23:32 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197567

Jilles Tjoelker <jilles@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jilles@FreeBSD.org

--- Comment #1 from Jilles Tjoelker <jilles@FreeBSD.org> ---
The error message ("No match") you get is from tcsh. It happens before chflags
is started, so chflags cannot do anything about it.

With sh, the error message is:

chflags: /var/empty/*: No such file or directory

A command like  chflags -f noschg /  correctly prints no error message and
returns exit status 0, however.

To me, the text in the man page

     -f      Do not display a diagnostic message if chflags could not modify
             the flags for file, nor modify the exit status to reflect such
             failures.

seems to match the behaviour I see: only failures to modify flags are
suppressed, while failures to locate files are unaffected. This matches chmod's
-f option, but that option is not standard either.

-- 
You are receiving this mail because:
You are the assignee for the bug.