From owner-freebsd-questions@FreeBSD.ORG Thu Nov 18 21:05:34 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A04016A4CE for ; Thu, 18 Nov 2004 21:05:34 +0000 (GMT) Received: from ns2.noanet.net (medusa.noanet.net [66.119.192.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id BED2A43D1F for ; Thu, 18 Nov 2004 21:05:33 +0000 (GMT) (envelope-from mksmith@noanet.net) Received: from noanet.lan (basilisk [64.146.175.5]) by ns2.noanet.net (8.13.1/8.13.1) with ESMTP id iAIL5LI3087477 for ; Thu, 18 Nov 2004 13:05:21 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Date: Thu, 18 Nov 2004 13:08:53 -0800 Message-ID: <6B628149FCE1B543A3AB351A29DC7D8E3A88AA@basilisk.noanet.lan> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Odd 'sudo' behavior with FreeBSD 4.10 Thread-Index: AcTNss4jkJ96SRJ5TkyRfSy8w3CTaw== From: "Michael Smith" To: Subject: Odd 'sudo' behavior with FreeBSD 4.10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 21:05:34 -0000 =20 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello: I've been able to replicate this on two separate machines, one with a clean install of 4.10 and one with an in-production upgrade from 4.7 to 4.10. In both cases it appears that using the 'sudo' command for any purpose, including downloading of files, moving of files, adding of users, etc. will sometimes fail due to the incorrect application of the UID and GID.=20 As an example, I 'sudo wget http://whatever' and 'sudo tar -zxvf' the file and it will show up with a numeric UID/GID that doesn't match anything in the password file. If I 'su root' and do the same commands, everything works fine. Has anyone seen this and, if so, do you know of a workaround or fix? Thanks, Mike - -- Michael K. Smith NoaNet 206.219.7116 (work) 866.662.6380 (NOC) mksmith@noanet.net http://www.noanet.net -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQZ0PZZzgx7Y34AxGEQJ7BACgnsW9ejT6VwGpN5LWZ5X2z2dk1J0An3E4 H310czaz4YI2yB5FiXxkoq7C =3DNNyd -----END PGP SIGNATURE-----