Share

nget

Code

Programming Languages: C++

License: GNU General Public License (GPL)

Repositories

browse code, statistics, last commit on 2008-03-10 cvs -d:pserver:anonymous@nget.cvs.sourceforge.net:/cvsroot/nget login

cvs -z3 -d:pserver:anonymous@nget.cvs.sourceforge.net:/cvsroot/nget co -P modulename

Show:

What's happening?

  • nget

    donut committed patchset 882 of module nget to the nget CVS repository, changing 1 files.

    2008-03-10 06:52:28 UTC by donut

  • Comment: Generic fcntl locking, for Solaris 10 and others

    Yeah, nfs.sf.net says it's worked since 2.6.5.

    2008-03-10 06:44:22 UTC by donut

  • nget

    donut committed patchset 881 of module nget to the nget CVS repository, changing 3 files.

    2008-03-10 06:41:58 UTC by donut

  • nget

    donut committed patchset 880 of module nget to the nget CVS repository, changing 2 files.

    2008-03-10 06:08:28 UTC by donut

  • Comment: Generic fcntl locking, for Solaris 10 and others

    Users of broken platforms can still use liblockfile, with its horrible sleep()'s, (or else don't keep the cache on NFS). I think there's no point in re-writing liblockfile. There's no fundamental reason why it shouldn't work. Maybe the bug is even fixed in Linux 2.6, and they just haven't updated the man pages yet?.

    2008-03-04 14:47:26 UTC by f2bruckman

  • Comment: Generic fcntl locking, for Solaris 10 and others

    So I was reviewing this a bit more and checked the open(2) man page, which says O_EXCL is broken on NFS. Using the symlink locking technique instead of opening with O_EXCL would work (though then it's a bit of a question as to why not just use the symlink lock for the file itself.. that wouldn't allow shared locks, but I don't think that's a huge problem.) The "big lock" could also be done,

    2008-03-04 12:11:40 UTC by donut

  • Comment: Generic fcntl locking, for Solaris 10 and others

    That's the reason. Unless you create a ".lock" file for every newsgroup in the overview, you'd still be vulnerable to a race condition, when the group's cache is first created, or even first re-created after a flush. That's admittedly improbable in practice -- I simply didn't care for the idea of leaving the ".lock" files about for aesthetic reasons. You could skimp on lock files, but not...

    2008-03-03 16:07:07 UTC by f2bruckman

  • Comment: Generic fcntl locking, for Solaris 10 and others

    This looks pretty complicated, I'm guessing the need for the .locked file is only to support removing the .locks file when there are no locks left? I wonder if it is really worth the effort, or if we could just leave .lock files around and simplify the code some?.

    2008-03-03 09:21:39 UTC by donut

  • Comment: Without-zlib option breaks the enable-checksum=method.

    As Frederick noted, the usegz option can be set to disable compression (or use a different level of compression.) Disabling zlib at configure time is only intended as a workaround on systems that don't have it (assuming any such systems exist ;), you should use the config option if you just want to disable the compression. Feel free to reopen the bug if the usegz option isn't working for...

    2008-03-03 08:03:21 UTC by donut

  • Comment: mode reader

    nget does set MODE READER, it just doesn't print it to the terminal (unless you set debug=2 in your ngetrc)

    2008-03-03 07:50:30 UTC by donut

Our Numbers