Date: Sun, 6 Jun 2004 15:56:07 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Tim Pushor <timp@crossthread.com> Cc: questions@freebsd.org Subject: Re: lseek problem Message-ID: <20040606205607.GF42830@dan.emsphone.com> In-Reply-To: <40C2B409.6070705@crossthread.com> References: <40C2B409.6070705@crossthread.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 06), Tim Pushor said: > I am working on porting an old system over to FreeBSD, and am having > a weird (to me) problem. This system uses various data file types, > and unfortunately it uses the group_id execution bit (but no execute) > on a data file to signify a sequential type file (mode 2440). I have > stepped through the code, and it is failing on an lseek > (fd,0,SEEK_SET) where fd is the properly opened file descriptor for > one of these files. This file is readable by the user and is about 2K > in size. this lseek should work shoudn't it? Its returning -1 and > sets errno to 22 (EINVAL). Could this be because of the weird mode? > man chmod doesn't say anything about what the set-group-id bit does > to non-executable files. Could this be the problem? The only obvious cause of EINVAL from lseek would be an invalid third argument. The program doesn't try and define SEEK_SET itself, does it? -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040606205607.GF42830>