From owner-freebsd-current Mon Nov 25 09:21:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19860 for current-outgoing; Mon, 25 Nov 1996 09:21:32 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA19804 for ; Mon, 25 Nov 1996 09:21:18 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vS4iR-0006oP-00; Mon, 25 Nov 1996 10:21:07 -0700 To: Marc Slemko Subject: Re: find and xargs in /etc/security Cc: current@freebsd.org In-reply-to: Your message of "Sun, 24 Nov 1996 23:15:07 MST." References: Date: Mon, 25 Nov 1996 10:21:07 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Marc Slemko writes: : Yuck. There is the little matter of sort which messes things up. There : are ways around it by adding another command to the pipe, but that starts : to get ugly. Hmm. Unless we just do a find -ls, but that means we don't : get the full timestamps. That's why I suggested that you fix it, since it looked non-trivial when I looked at it. If you can come up with an easy way to deal with this, then please let me know. Taking a closer look, I don't think the sort is required at the place that it is right now, since I think it can be done after the xargs safely. : There is more wrong with /etc/security than that, so perhaps it is worth : looking at it a bit more deeply. OpenBSD and NetBSD have a far more : comprehensive /etc/security. Can you elaberate as to what makes them better? Warner