From owner-freebsd-questions Thu Feb 23 18:19:10 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA22596 for questions-outgoing; Thu, 23 Feb 1995 18:19:10 -0800 Received: from warlock.win.net (warlock.win.net [198.30.130.3]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA22590 for ; Thu, 23 Feb 1995 18:19:08 -0800 Received: (from bugs@localhost) by warlock.win.net (8.6.9/8.6.9) id VAA24546 for questions@freebsd.org; Thu, 23 Feb 1995 21:20:07 -0500 From: Mark Hittinger Message-Id: <199502240220.VAA24546@warlock.win.net> Subject: re: majordomo & perl To: questions@FreeBSD.org Date: Thu, 23 Feb 1995 21:20:07 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 761 Sender: questions-owner@FreeBSD.org Precedence: bulk I have set up a few of the perl things (majordomo, ftpmail, gopermail) ect. The biggest problem seems to be in the file locking mechanism that each of these packages seem to use. The lockf code in perl seems to be bogus: eval.c: if (fp) { argtype = (int)str_gnum(st[2]); value = (double)(flock(fileno(fp),argtype) >= 0); } value returns 1 if the lock is ok. some perl code I have expects a zero return if the flock is ok. it is an easy change but I don't know enough about perl's innards to suggest everybody fix it :-) ftpmail used fcntl with 32 bit off_t's for locks. This is also a slight problem in the freebsd world. I nearly have the latest majordomo in the air so it is not a big deal. Good Luck Mark Hittinger bugs@win.net