From owner-freebsd-questions Tue Nov 28 15:38: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from marine.sonic.net (marine.sonic.net [208.201.224.37]) by hub.freebsd.org (Postfix) with SMTP id 3D30D37B400 for ; Tue, 28 Nov 2000 15:37:58 -0800 (PST) Received: (qmail 11138 invoked from network); 28 Nov 2000 23:37:29 -0000 Received: from sub.sonic.net (208.201.224.8) by marine.sonic.net with SMTP; 28 Nov 2000 23:37:29 -0000 Received: from sonic.net (wingerboy [209.204.177.11]) by sub.sonic.net (8.11.0/8.8.5) with ESMTP id eASNbO424545 for ; Tue, 28 Nov 2000 15:37:24 -0800 X-envelope-info: Message-ID: <3A2441A9.18C49626@sonic.net> Date: Tue, 28 Nov 2000 15:37:13 -0800 From: Kelsey Cummings Reply-To: kgc@sonic.net Organization: sonic.net X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: 4.2 crontab problems? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When a user edits thier crontab (crontab -e) on a recently upgraded 4.2 box, they get this error: "crontab.ALkxt20176" 4L, 313C written crontab: temp file must be edited in place Root can, however, run `crontab -u user -e` and it works just fine. Any suggestions? Did I miss something? Cron Daemon wrote: > > SNMP Error: > Received SNMP response with error code > error status: noSuchName > index 1 (OID: 1.3.6.1.2.1.2.2.1.10.4) > SNMPv1_Session (remote host: "sms" [208.201.224.10].161 > community: "public" > request ID: 1597123035 > PDU bufsize: 8000 bytes > timeout: 2s > retries: 5 > backoff: 1) > SNMPGET Problem for ifInOctets.4 ifOutOctets.4 sysUptime sysName on public@sms -- Kelsey Cummings - kgc@sonic.net sonic.net System Administrator 300 B Street, Ste 101 707.522.1000 (Voice) Santa Rosa, CA 95404 707.547.2199 (Fax) http://www.sonic.net/ Fingerprint = 7F 59 43 1B 44 8A 0D 57 91 08 73 73 7A 48 90 C5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message