From owner-freebsd-bugs Mon Apr 15 11:12:07 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA16256 for bugs-outgoing; Mon, 15 Apr 1996 11:12:07 -0700 (PDT) Received: from pelican.altadena.net (pelican.altadena.com [206.16.90.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA16251 for ; Mon, 15 Apr 1996 11:12:02 -0700 (PDT) Received: by pelican.altadena.net (Smail3.1.29.1 #10) id m0u8skh-0000ReC; Mon, 15 Apr 96 11:11 PDT Message-Id: From: pete@pelican.altadena.net (Pete Carah) Subject: AT problem under CRON To: bugs@freebsd.org Date: Mon, 15 Apr 1996 11:11:51 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If I use cron to run a periodic job for a *non-root* user, and that job uses 'at', the resulting at jobs *all* fail for a mismatched mail-to. Looking through the sources, it looks like either cron doesn't set both euid and reuid, or at least something like that (I added LOGNAME and USER pointing to the correct non-root user name) to the script to no avail). I've attacked it in the source (atrun - making that message a warning rather than a fail, though it is somewhat of a security thing; I think that this is truly the wrong place to fix it) but there needs to be some change to either cron, at, or atrun (or a combination) to fix it. I can't believe that noone else has ever tried this :-) Sorry for not using the submit-bug but I don't know the category since this package falls into more than one class as distributed. -- Pete