Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: "lubkt@spectrum.CC.Lehigh.EDU"@vax1.cc.lehigh.edu
Newsgroups: comp.sys.sun
Subject: Quota under Sun
Keywords: No Digest Subjects in Unmoderated Mode
Message-ID: <2951@brchh104.bnr.ca>
Date: 4 Jun 91 18:40:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sunspots, Psuedo-Unmoderated
Lines: 21
Approved: sun-spots@rice.edu
X-Original-Date:    Tue, 30 Apr 1991 11:04 EDT

For a Sun Sparc 1+, SunOS version 4.1.1:

If quota is  enforced  on a  file system, how  do you set the timer so
that logins are disabled after the  time has elapsed? I've tried using
`edquota -t' for /usr2 (where user files are stored),  and have set it
to 3 days.   But when I  do `/usr/etc/repquota -v  /usr2', I still get
entries  like  "NOT STARTED" under   timeleft  column  for users  with
exceeded quota. For a long time, I had not set any  time limit, so the
entries for  users with exceeded quota  had timeleft as "NOT STARTED",
and   that  made sense.  But  now,  after  I have   set the timelimit,
shouldn't  this  be changed.  I  tried running `/usr/etc/quotacheck -v
/usr2' and restarted rpc.quotad but these  didn't  help. Do I  need to
reboot? Something I  don't like to  do  especially during the last few
weeks of the semester.  Any suggestions?
--

Binod Taterway                     |    lubkt@spectrum.CC.Lehigh.EDU
Sr. User Consultant                |    bt00@lehigh.BITNET
Lehigh University Computing Center |    (215) 758-3984 (off)
Bethlehem, PA 18015                |    (215) 758-4983 (fax)