From owner-freebsd-questions Mon Oct 1 15:55: 8 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id 3299A37B407 for ; Mon, 1 Oct 2001 15:55:05 -0700 (PDT) X-Real-To: Received: from ALEX (ip88-85.adsl.wplus.ru [195.131.88.85]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id CAA99493 for ; Tue, 2 Oct 2001 02:54:59 +0400 (MSD) Date: Tue, 2 Oct 2001 03:00:12 +0400 From: support X-Mailer: The Bat! (v1.52f) Personal Reply-To: support Organization: Majordomo.ru X-Priority: 3 (Normal) Message-ID: <6555968124.20011002030012@majordomo.ru> To: freebsd-questions@FreeBSD.ORG Subject: quotactl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi people, I've faced the following problem: rewriting the perl script on c/c++ (used cc and gcc compilers) I need the quotactl system call to get group quotas. While everything was fine on the testing machine - no problem at all - when I tried to compile and run it on the main PC I found out that the quotas are not calculated at all (looks like the numbers are taken from nowhere or are just zero) - dqb_curblocks value was either some weird figures or just 0. The last error value was 22, corresponding to the invalid argument. That is the string that does not work: quotactl ("/home", QCMD(Q_GETQUOTA, GRPQUOTA), grp_id, &dqbuf); By the way, declarations as struct dqblk dqbuf; and int grp_id; are made as well as all necessary includes. PC where all worked Ok has FreeBSD 4.3-Stable PC where it failed: FreeBSD 4.3-Release. Also, standard quota utility is working absolutely fine on both machines. Can anybody help me with that? Best regards, Valery Zvonaryov mailto:support@majordomo.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message