Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!ssbell!kent From: kent@ssbell.UUCP (Kent Landfield) Newsgroups: comp.sources.d Subject: Re: A few questions/comments on Rkive Keywords: long rkive archive sources USENET Message-ID: <521@ssbell.UUCP> Date: 12 Jul 89 04:23:22 GMT References: <1123@ssp15.idca.tds.philips.nl> <520@ssbell.UUCP> <1129@ssp15.idca.tds.philips.nl> Reply-To: kent@ssbell.UUCP (ssbell Admin) Organization: Sterling Software, FSG-IMD, Bellevue, NE. Lines: 71 First off, sorry for the delay in getting this response out. I finallly took a *real* vacation. First in at least 3 years... :-) Anyway...... In article <1129@ssp15.idca.tds.philips.nl> jos@idca.tds.PHILIPS.nl (Jos Vos) writes: # I already looked in the code and saw that it would be quite easy # to add an archive method that popen's a user program (specified in some # way) that puts a plain filename on stdout. # Than I can play with SysV date +%... as much as I like. # The next step could be to let that program generating a relative # pathname, in that case the program could be just a script with # date '+volume%y/%h/%y%m%d' # Only the problem with the .seq suffix should be solved then, # if you *want* to solve it. I see that the "hook" is apparent to you as well... :-) In article <520@ssbell.UUCP> I wrote: # The test as to whether an article is already archived is done by checking # if the archive file exists. I'm not sure what you mean by BIG. ... Jos Vos writes: # I only meant that the previous item (generating own filenames) would # cause that you can't detect an article --- filename-for-saving relation # anymore. Doesn't that problem also occur in your proposed scheme? # What about the .archived file mentioned somewhere in the documentation? The problem does not occur with the Chronological archiving. As for the .archived file, it is used to indicate what the status is of the articles currently on the system waiting to be expired. If an article is expired, the entry in the .archived file is removed. In this way the .archived file for the newsgroup is self-maintaining (i.e. it does not grow out of bounds) and is *not* a log of all previous "article number - archive resting place" entries. The .archived file is used so that an article is only archived once, the first time rkive is run after the article reaches the system. I wrote: # Currently, crosspostings are *not* handled. ... Jos Vos writes: # It becomes a problem if you want to use rkive for archiving a lot of # newsgroups, i.e. not only sources. But I can imagine it's quite # difficult to handle that correctly (w.r.t. the rkive.cf file's lists). No, it really will not be too hard since I just need to check if the group the article is crossposted to is also being archived and act accordingly. At this point it just has not been done because I have not been able to find the time. It is currently not a problem as long as you have disk space. :-) :-) You will not lose any articles, just duplicate them. :-( Jos Vos writes: # Is it not possible to use rkive as a program directly # from the sys file (that is, with the article as stdin)? I wrote: # No. rkive is meant to run from cron and not receive the articles from stdin. Jos Vos writes: # Still a nice item for the IDEAS file :-) Granted. The only problems that I see here is that I need some information about where to archive, modes, owners etc that could make the command line real ugly... :-) It can be worked but it is not real high on the priority list. It has been put into the IDEAS file for now... -Kent+ --- Kent Landfield UUCP: kent@ssbell Sterling Software FSG/IMD INTERNET: kent@ssbell.uu.net 1404 Ft. Crook Rd. South Phone: (402) 291-8300 Bellevue, NE. 68005-2969 FAX: (402) 291-4362