From: Alex Riesen <alexander.riesen@synopsys.COM>
To: mdew <mdew@orcon.net.nz>
Cc: linux-kernel@vger.kernel.org, chuchelo@krasu.ru
Subject: Re: File still being accessed?
Date: Thu, 12 Dec 2002 12:37:38 +0100 [thread overview]
Message-ID: <20021212113738.GB1647@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <1039690223.463.11.camel@nirvana>
mdew, Thu, Dec 12, 2002 11:50:19 +0100:
> > > Under Linux 2.5.51 Ive noticed that Downloader4X (Getright-type for
> > > linux) http://www.krasu.ru/soft/chuchelo/
> > >
> > > when trying to resume a file, It thinks the file is still being
> > > accessed, however under 2.4, it has no such problem. Is this a bug in
> > > 2.5.x still? any patches available that could help?
> > which d4x version, what _exactly_ the message states?
> > -alex
> I've tried both D4X GTK2 (2.4.0-rc1) based and GTK1.2.x (1.3.0) based, same results.
>
> I add a download, let it partially download, then press
> "Continue/Restart Downloads"
>
> -> Retry 1 ...
> -> Trying to connect...
> -> Socket was opened!
> -> Trying to create a file
> + File was created!
> !! File is already opened by another download!
> !! Downloading was failed...
The problem is advisory file locking. I'll try to debug
it later, but something changed in how
fcntl(fd, F_SETLK,{...,F_WRLCK,...}) works. It return an
error now. Or maybe d4x just fails to unlock it, it doesn't
check if unlock failed.
The program doesn't show the real value of errno, just
handles EINVAL and ENOLCK, so exact analisys is not possible
apart something bad happened ("is already opened").
The EINTR case, for instance, would cause similar behaviour.
I suppose d4x just incorrectly uses it, but cannot say anything
for sure.
The maintainer is notified.
-alex
next prev parent reply other threads:[~2002-12-12 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 4:03 mdew
[not found] ` <20021212085229.GA1647@riesen-pc.gr05.synopsys.com>
2002-12-12 10:50 ` mdew
2002-12-12 11:37 ` Alex Riesen [this message]
2002-12-13 10:43 ` mdew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021212113738.GB1647@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=chuchelo@krasu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mdew@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®