Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!nike!ucbcad!ucbvax!engvax.UUCP!PORTIA From: PORTIA@engvax.UUCP (Portia 616-2635) Newsgroups: mod.computers.vax Subject: summary of ways to restricting printing over decnet Message-ID: <8609190205.AA24375@csvax.caltech.edu> Date: Thu, 18-Sep-86 18:59:19 EDT Article-I.D.: csvax.8609190205.AA24375 Posted: Thu Sep 18 18:59:19 1986 Date-Received: Sat, 20-Sep-86 09:58:42 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 36 Approved: info-vax@sri-kl.arpa > ...We would like to restrict the copying of files to ... [a laser] printer > over DECnet or otherwise to charge the users properly. Does anyone have a > solution? I submitted this question to the net a while back and have received many suggestions so far, the most common suggestion being a variation of $SET ACL/OBJ=DEV/ACL=(IDENT=user,ACCESS=NONE) txnn: Unfortunately, ACL does NOT work on a spooled queue! I suppose this is a bug that should be SPR'ed. However, we could do the following: >... Just don't make the device spooled! >The queues and associated commands will work just fine - all that won't work >is copying directly to the device, which will always fail to allocate the >device...Or, spool the device to a disk on which the DECnet default account >has no quota. this can be set up, even though we don't enable quota currently. > Or we could use proxy and/or get rid of the default decnet account. > It has drawbacks: > > - You have to disable ALL default access to the system or people > will just specify a null account (NODE""::) and avoid the > proxy; > - You have a lot of administrative overhead maintaining all those > accounts you might otherwise have never created. > - there are other reasons for keeping the default decnet account... Thanks for all the suggestions. -- Portia Bjorndahl UUCP -- {allegra|ihnp4}!scgvaxd!engvax!portia Hughes Aircraft Co. ARPA -- engvax!portia@csvax.caltech.edu (213) 616-2635