Date: Wed, 01 Mar 2006 13:27:25 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: Boris Samorodov <bsam@ipt.ru> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: mpack-1.6 Message-ID: <BDC46C39FADF0DDF8CFBCDA3@utd59514.utdallas.edu> In-Reply-To: <18666752@srv.sem.ipt.ru> References: <44050D77.2030503@j2d.lam.net.au> <BCA5F50D2461133FF65B3BD8@utd59514.utdallas.edu> <84747890@srv.sem.ipt.ru> <C0D04BDAC59820A93DC4E43F@utd59514.utdallas.edu> <18666752@srv.sem.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Wednesday, March 01, 2006 22:21:35 +0300 Boris Samorodov <bsam@ipt.ru> wrote: >> > >> I've already incorporated that patch in to the other one and deleted >> it, but that doesn't fix this bug. > > Hm: > > ----- ># uname -a > FreeBSD srv.sem.ipt.ru 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Feb > 28 22:21:02 MSK 2006 bsam@srv.sem.ipt.ru:/usr/obj/usr/src/sys/SRV > i386 > ># cd /usr/ports/converters/mpack ># rm files/patch-unixpk_c > (Makefile,v 1.18) ># make > ... ># cd work/mpack-1.6 ># mkdir /usr/tmp ># ./mpack -s "test" Makefile bsam@ipt.ru ># > ----- > > That's it. With that patch I've got "File exists" error. > Double check you additional patches? > Again, all the patches do is change a hard-coded path for TMPDIR from "/usr/tmp" to "/tmp". They don't change anything else. The program, bulit from source, fails with a "File or directory not found" error because the hard-coded path, "/usr/tmp", does not exist. When you fix *that* problem (by applying my patches), you get a different error, "File already exists", in the same place in the code. There's a bug in the program that is not allowing the program to open a file in "/tmp" and write to it, then complete its work and exit successfully. My problem is, I'm not a programmer, and my C skills are not that good, so I'm having problems figuring out what's causing the error (other than the fact that I know it creates the file, and then, when it tries to write to it, complains that the file already exists (which seems kind of silly to me.) There's not a problem with my patches, AFAICT, there's a problem with the program. If there's any programmers on this list, who have the time, I could use some help tracking this down. I emailed the developers, but I don't know if they'll get back to me or not. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ir/security/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BDC46C39FADF0DDF8CFBCDA3>