On Sun, Nov 07, 1999 at 05:44:51PM +0900, Daniel C. Sobral wrote:
> Actually, use fstat to check against ftpd, and lockf between the
> scripts. :-)
Good idea :) I think that I'll do just that.
Cheers,
--
Jos Backus _/ _/_/_/"Modularity is not a hack."
Jos Backus wrote:
>
> Scanning the directory for new files, as the aforementioned script does. If
> you have more than one script doing this at the same time, both may conclude
> that a given file is ``available'' and try to act upon it. Inevitably, one of
> those scripts will fail. Hence my solu
On Fri, 05 Nov 1999 12:09:18 +0100, Jos Backus wrote:
> I'm in the anti-bloat camp, and I agree with this sentiment.
What would be more interesting, I think, is investigating the use of
locking by default. One wonders what it'd break, and how we'd work
around it. ;-)
Ciao,
Sheldon.
To Unsu
On Fri, Nov 05, 1999 at 12:58:42PM +0200, Sheldon Hearn wrote:
> Then it's your _script_ that should do careful locking to avoid tripping
> up over itself, surely? :-)
Yeah, in fact it does, it uses lockf ;-p
> Let me take a step back. I'm not saying that what you're doing to ftpd
> is wrong.
On Fri, 05 Nov 1999 11:39:29 +0100, Jos Backus wrote:
> Scanning the directory for new files, as the aforementioned script does. If
> you have more than one script doing this at the same time, both may conclude
> that a given file is ``available'' and try to act upon it.
Then it's your _script
On Fri, Nov 05, 1999 at 12:18:21PM +0200, Sheldon Hearn wrote:
> Then use fstat. :-)
OK, OK :)
> I think you've developed a complex solution to a more simply solved
> problem. UNIX offers you lots of little tools for good reason. Adding
> functionality to ftpd that is available through other t
On Fri, 05 Nov 1999 11:15:18 +0100, Jos Backus wrote:
> > So fstat(1) doesn't show you that the file is opened to ftpd?
>
> No, it does indeed show that.
Then use fstat. :-)
> It seems a more natural solution to me than grepping for ftpd in fstat's
> output regarding the file.
I think you'v
> So fstat(1) doesn't show you that the file is opened to ftpd?
No, it does indeed show that.
> You really have to lock the files to help you with this problem?
It seems a more natural solution to me than grepping for ftpd in fstat's
output regarding the file. Also, I think that approach introd
On Thu, 04 Nov 1999 23:05:30 +0100, Jos Backus wrote:
> This patch adds a ``-x'' flag to ftpd, which instructs ftpd to obtain
> an exclusive lock on files it commits to disk as a result of a store
> operation. This way it becomes easy to tell whether a download has
> finished, in case the file
9 matches
Mail list logo
