FreeBSD Port: mpack-1.6
bsam at ipt.ru
Wed Mar 1 11:01:07 PST 2006
On Wed, 01 Mar 2006 10:00:14 -0600 Paul Schmehl wrote:
> --On Wednesday, March 01, 2006 13:56:55 +1100 Nik Lam
> <freebsdnik at j2d.lam.net.au> wrote:
> > Hi,
> > I'm having trouble running the latest mpack (1.6) on FreeBSD 5.4.
> Since posting the patches last night, that changed the "/usr/tmp" path
> to "/tmp" in some source files, a new problem has emerged.
> If you do this:
> ktrace mpack -s "Testing" Makefile pauls at utdallsa.edu
> It results in this:
> |\uffff(\uffff\uffff\uffff\uffff\uffff&(\uffff(: File exists
> Ktrace shows this:
> 79012 mpack CALL open(0x804f060,0xa02,0x1a4)
> 79012 mpack NAMI "/tmp/mpackCl8rPI"
> 79012 mpack RET open -1 errno 17 File exists
> 79012 mpack CALL writev(0x2,0xbfbfcb20,0x4)
> 79012 mpack GIO fd 2 wrote 31 bytes
> 0x0000 7c90 1328 f4d3 bfbf e026 0528 a414 0728 ||..(.....&.(...(|
> 0x0010 013a 2046 696c 6520 6578 6973 7473 0a |.: File exists.|
> 79012 mpack RET writev 31/0x1f
> 79012 mpack CALL exit(0x1)
> I've looked through the source code, but I'm not sure where the
> problem is. I only see one call to open the file.
No. Lookup before mpack reads Makefile.
> Can someone help?
Can't say for sure why that patch exists, but deletting
files/patch-unixpk_c should help. Cvs says "Yet another overflow
check, better temp file name & misc cleanups". Assume this comment is
for the whole commit.
Boris B. Samorodov, Research Engineer
InPharmTech Co, http://www.ipt.ru
Telephone & Internet Service Provider
More information about the freebsd-ports