Your message dated Tue, 02 Aug 2005 02:47:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#13603: fixed in at 3.1.9
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Oct 1997 17:16:08 +0000
Received: (qmail 7880 invoked from network); 4 Oct 1997 17:15:50 -0000
Received: from zed.ludd.luth.se ([EMAIL PROTECTED])
  by 205.229.104.5 with SMTP; 4 Oct 1997 17:15:50 -0000
Received: from brother.ludd.luth.se.ludd ([EMAIL PROTECTED] [130.240.16.78])
        by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id SAA10085
        for <[EMAIL PROTECTED]>; Sat, 4 Oct 1997 18:18:01 +0100
From: Martin Str|mberg <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Subject: at does not work if /var is nfs mounted
To: [EMAIL PROTECTED]
Date: Sat, 4 Oct 1997 19:17:59 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Package: at
Version: 3.1.7-3

at does not work if /var is nfs mounted.

kant:/var/tmp> at 2:2
Cannot access /var/spool/cron/atjobs: Permission denied

In the nfs log on the server (created by running "/usr/sbin/rpc.nfsd -F
-d call >/var/tmp/nfsd.log 2>&1"), while I'm doing this, I see:
[...]
nfsd[3388] 09/28/97 17:42       new_fh = /var/clients/kant/var/spool/cron/atjobs
nfsd[3388] 09/28/97 17:42 result: 0
nfsd[3388] 09/28/97 17:42 lookup [1 97/9/28 17:42:20 kant 0.100+100,4,24,25,29]
        fh:/var/clients/kant/var/spool/cron/atjobs n:.SEQ
nfsd[3388] 09/28/97 17:42       new_fh = 
/var/clients/kant/var/spool/cron/atjobs/.SEQ
nfsd[3388] 09/28/97 17:42 result: 0
nfsd[3388] 09/28/97 17:42 getattr [1 97/9/28 17:42:20 kant 0.100+100,4,24,25,29]
        /var/clients/kant/var/spool/cron/atjobs/.SEQ
nfsd[3388] 09/28/97 17:42 result: 0
nfsd[3388] 09/28/97 17:42 read [1 97/9/28 17:42:20 kant 0.100+100,4,24,25,29]
        /var/clients/kant/var/spool/cron/atjobs/.SEQ: 4096 bytes at 0
nfsd[3388] 09/28/97 17:42 result: 0
nfsd[3388] 09/28/97 17:42 write [1 97/9/28 17:42:20 kant 0.100+100,4,24,25,29]
        /var/clients/kant/var/spool/cron/atjobs/.SEQ: 6 bytes at 0
nfsd[3388] 09/28/97 17:42 result: 0
nfsd[3388] 09/28/97 17:42 lookup [1 97/9/28 17:42:20 kant 0.100+100,4,24,25,29]
        fh:/var/clients/kant/var/spool/cron/atjobs n:a0001d00dea622
nfsd[3388] 09/28/97 17:42 result: 2
nfsd[3388] 09/28/97 17:42 lookup [1 97/9/28 17:42:20 kant 
1000.100+100,4,24,25,29]
        fh:/var/clients/kant/var/spool/cron/atjobs n:a0001d00dea622
nfsd[3388] 09/28/97 17:42 result: 13
nfsd[3388] 09/28/97 17:42 lookup [1 97/9/28 17:42:27 kant 0.0+0]
        fh:/var/clients/kant/var n:log
[...]

Note that there are two lookups for the file a0001d00dea622, the first one
fails with ENOENT (which is what at expects) then there is a second lookup
with uid != 0, which fails with EACCES, because uid 1000 is not root.
It's this error at sees.

I've trace this problem to the swapping of uid and euid at often does, using
defines from at-3.1.7/privs.h; or the kernel that does a second lookup if
the first one fails with uid instead of fsuid (hmm, perhaps fsuid == euid?).


Thanks,

                                                        MartinS
---------------------------------------
Received: (at 13603-close) by bugs.debian.org; 2 Aug 2005 09:54:40 +0000
>From [EMAIL PROTECTED] Tue Aug 02 02:54:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1DztMg-0001Gj-00; Tue, 02 Aug 2005 02:47:14 -0700
From: Ryan Murray <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#13603: fixed in at 3.1.9
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 02 Aug 2005 02:47:14 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 4

Source: at
Source-Version: 3.1.9

We believe that the bug you reported is fixed in the latest version of
at, which is due to be installed in the Debian FTP archive:

at_3.1.9.dsc
  to pool/main/a/at/at_3.1.9.dsc
at_3.1.9.tar.gz
  to pool/main/a/at/at_3.1.9.tar.gz
at_3.1.9_i386.deb
  to pool/main/a/at/at_3.1.9_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Murray <[EMAIL PROTECTED]> (supplier of updated at package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  2 Aug 2005 02:34:45 -0700
Source: at
Binary: at
Architecture: source i386
Version: 3.1.9
Distribution: unstable
Urgency: low
Maintainer: Ryan Murray <[EMAIL PROTECTED]>
Changed-By: Ryan Murray <[EMAIL PROTECTED]>
Description: 
 at         - Delayed job execution and batch processing
Closes: 13603 17561 53586 61604 68364 70928 70988 79650 84351 84791 130023 
133812 142810 153700 162677 173635 175211 193396 194674 200627 202617 205523 
220336 239394 251058 257074 269440
Changes: 
 at (3.1.9) unstable; urgency=low
 .
   * Apply rewritten parser patch (closes: #70928)
   * Several changes to be more SUSv3 compliant (closes: #133812)
   * Remove yacc/flex generated files, and remove them in the clean target
   * Remove /usr/doc handling from scripts (closes :#261467)
   * use chown with : instead of . (closes: #205523)
   * Add two precisions to format strings (closes: #220336)
   * Fix manpage typos (closes: #153700, #175211)
   * Use --retry option of start-stop-daemon (closes: #84351)
   * Create /var/spool/cron/atjobs/.SEQ in the postinst (closes: #142810)
   * Always rescan the queue after signals (closes: #194674)
   * use 89 11 as parameters to update-rc.d defaults (closes: #200627)
   * hold privs longer when creating pid file (closes: #13603)
   * Add stdio.h for stderr to parsetime.y (closes: #130023)
   * Use invoke-rc.d in maintainer scripts (closes: #162677)
   * Allow usernames > 8 characters.  Don't write out usernames with at that
     atd will later call corrupt (closes: #17561)
   * Run as user daemon, rather than root (from 3.1.8-11ubuntu3) (closes: 
#251058)
     + Derooted /usr/bin/at.
     + at.c:
       - Keep real uid, only switch to daemon gid when unlinking files (the
         directory is daemon-group writeable, but the job files are owned by 
user).
       - Instead of creating the job file and then fchown()'ing it (which does
         not work when running as non-root), change to the real gid when
         creating the file.
     + atd.c:
       - Don't check that the file gid is equal to the execution gid (since job
         files are now always owned by "daemon".
       - setgid() to the user's gid, not to the file gid for job execution.
     + debian/rules:
       - Install /usr/bin/at as daemon:daemon 6555 instead of root:root 4755
         (running as user daemon is necessary to be allowed to send a signal to
          atd.)
       - Install /etc/at.deny as root:daemon 640 instead of root:root 0600.
     + debian/postinst:
       - Make /var/spool/cron/{atjobs,atspool} writeable for group "daemon".
       - Update permissions of /etc/at.{allow,deny} if we upgrade from a 
previous
         version and there is no statoverride for these files.
   * Update standards version (closes: #239394)
   * Increment tm_mday for at "time" case, rather than hardcoded increment of
     a day in seconds.  (closes: #61604)
   * Print usage on "at -c" (closes: #202617)
   * Increment tm_year when the month and day are earlier than current
     (closes: #79650)
   * Drop ISO timeformat; following SUSv3 instead (closes: #53586)
   * Add optional PAM support based on the submitted patch (closes: #68364)
   * Use AC_FUNC_GETLOADAVG and getloadavg.c from XEmacs, so that the
     system function is used first, then the getloadavg.c from at if it isn't
     available (closes: #269440)
   * Fix permissions of /var/spool/cron/at* in the deb files to match what is
     used now
   * Remove /usr/sbin/atrun; the packaging is set up for running as a daemon.
   * Align batch(1) with SUSv3 by accepting no arguments (closes: #70988)
   * Update description of -v option to clarify that it prints the time
     before the job submission starts (closes: #257074)
   * Update description of submission to uppercase queues (closes: #84791)
   * Update atq format description (closes: #193396)
   * Return EXIT_FAILURE if one jobid fails for -c and -r (closes: #173635)
Files: 
 d1df85e6898471736141ccb54fb7ddc6 501 admin important at_3.1.9.dsc
 795f1d7ba2f77c5d85ec3e5abe6da46c 97949 admin important at_3.1.9.tar.gz
 3b015ac30f98e55cb9a3972329a12445 41522 admin important at_3.1.9_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC7z94N2Dbz/1mRasRAmz/AJ9U4XzfhawSEJhew/1nZPVxClVBYACfUsNn
+98uyJlwah5ywRystSzuOlU=
=E7Hk
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to