> > The switches "stayondomain" and "stayonhost" doesn't seem to work. > > It still plucks pages beyond what I set it to do. When my logs were set > > to extensive, this error shows up: > > > > Processing http://mobile.theonion.com/... > > Retrieved ok. > > Ignoring invalid link attribute 'stayondomain' > > Ignoring invalid link attribute 'stayondomain' > > Ignoring invalid link attribute 'stayondomain' > > I don't see "stayondomain" in the docs, the helpfile, or the > source. "stayonhost" is in all of them and should work.
Tony is bang on. 'stayondomain' doesn't exist yet. It has been in the parser wishlist for about a year, but no one skilled enough has had a chance to implement it yet. Any takers? I will ship a fresh bottle of Bailey's to anyone who can help out ;-) > > b) Scheduler - I've set a channel to update at 5am. Due to the fact > > that there's *quite* a lot of stuff to download (about 1000++ items), it > > takes quite a bit of time. This results in Plucker Desktop loading up > > another instance of the plucking software to pluck the exact same channel > > (It says Channel is due). Is there something that stops Plucker Desktop > > from loading another instance of the same channel? If you are using the progress dialog then a new process wont't pop up during the process (though this was fixed only recently). And if you are using either progress dialog or console progress from the commandline plucker- desktop, it should be impossible for this to happen, since there is no timer running, and hence no possibility of starting a new update batch. It will occur however (currently), if you are using console progress windows and plucker- desktop in non-commandline mode. This is because the console windows are asynchronous, there is no way for Plucker Desktop to know when the final channel in the batch is terminated (and hence to know when safe to turn on/off the faucet to allow a new update to initiate). In the progess dialog, we do track the termination of each update because they are piped processes there, and we thus get an event notification when the processes terminates. I am still thinking of the best way for the console windows. The best that I can come up so far is to have a message dialog that says 'click here when you are done', that will reallow a new autoupdate to start when you click it. <memory usage> The distiller uses a good deal of memory since there is a lot of links and information to manage. Stopping a second instance from initiating, as you mention, is the best solution. Best wishes, Robert .---~~~~~~---. ________________________________________ / \ / \ MedicalMnemonics.com | __ | .-------+` `+-------. A free non-profit online searchable | | () | | database of medical mnemonics to help `-------+.__.+-------' remember the important details. (| O O |) ^\ /^ http://www.medicalmnemonics.com \ \ / / [EMAIL PROTECTED] \ ~~~~ / ________________________________________ `-_ _-' ~~~~~~ _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
