[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Bug: I thought this was fixed
- Subject: RE: [cobalt-users] Bug: I thought this was fixed
- From: "Dan" <dan@xxxxxxxxxxxxx>
- Date: Mon Jan 17 17:55:33 2000
> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of David Sexton
> Sent: Monday, January 17, 2000 4:50 AM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-users] Bug: I thought this was fixed
>
>
> Dan wrote:
> >
> > Undefined subroutine &main::repquota called at
> /usr/local/sbin/monitor line
> > 255.
>
> This comes about from manually playing with quotas (quotaed). I have
> 'fixed it in /usr/sbin/monitor by wedging the function
> 'getGoodSiteAdmins'.
>
> The 'proper' way of fixing it would be to find out which
> user's quota
> has been changed and then reset it using the Cobalt UI. If this is
> inconenient (or you don't use the Cobalt UI anymore) try the following :
>
> Two points of warning :-
>
> DON'T DO THIS unless you are comfortable with PERL & UNIX.
>
> DON'T DO THIS unless you are happy not just invalidating but
> thoroughly smashing your software warranty....
>
> sub getGoodSiteAdmins
> # Args: vsite group
> # Return value: list of vsite admins whose usage < soft
> {
> my ($group) = @_;
>
> return grep {
> # my ($usage,$soft,$hard) = repquota($_, 0);
> my ($usage, $soft, $hard) = (10, 20, 30); # Wedge it fixed.
> ($usage < $soft);
> } vsite_admin_list(vsite_get_bygroup($group));
> }
>
> This gets confused when the cobalt user database gets out
> of sync with
> the actual quotas on disk. This fix will (I think) disable all of the
> 'user is close to or over quota' emails, but the actual quota will still
> be enforced on disk.
>
>
In this case, I had never touched the quotas except via the GUI. I created
this site, gave it 5MB of space and then the user uploaded a ton of huge
.jpg images, (scanned book pages).
I started getting the error message and when I upped the site to 10MB, it
stopped.
An old post on the list said this was fixed in update 1.1. I figured it was
included in one of the newer updates that is on this RAQ2 that I'm using.
--
Dan Kriwitsky