![]() ![]() ![]() You can see the RSS feeds we've got set up at the top of this page. As we set these new feeds up, we'll let you know. For example, if a new Prayer Diary or news bulletin is added to the site, and you want to include it in your parish magazine, subscribing to the appropriate RSS feed will save you having to keep checking. ![]() There may be content on the website you want to be reminded about when it gets updated. Usually, clicking on this takes you to the RSS feed. There are several different designs of RSS icons, but they are all very similar. If you have subscribed to an RSS feed, every time new content is added to the page covered by that feed, you’ll receive an alert. RSS feeds are a very common way of allowing website users to keep track of new content. Or you can still use the raw RSS feeds, as described below. UPDATE: All of these can now be followed using our subscription service which sends an email when updates are available. Hope this information might be useful to someone else in the future.At the moment, we have the following RSS feeds: Rssowlnix.exe -vmargs -vm “%JAVA_HOME%\bin” -server -Xms32m -Xmx4096m -Xss128k -XX: UseParallelGC -XX: UseParallelOldGC -Dosgi.requiredJavaVersion=1.8 -Drssowl.reindex=true When attempting to repair a (large) corrupted database, the program uses quite a bit of memory as well for that process (more than the program would use normally), and the default command line parameter from the github FAQ ( ) is not sufficient, thus this adjusted parameter sufficiently solves that problem: This is no problem either, as adding/editing only the following lines in the ‘RSSOwlnix.ini’ file in the program directory solves that (any other values in the *.ini file you would leave alone as default): ![]() Naturally when working with a large database, the program requires some tweaks (in contrast to its default configuration), because when the database approaches some undetermined size (which I never made a mental note of), the program will start to malfunction when trying to launch the program (because it will run out of memory). However, it should be noted that I do still experience corruption issues IF the computer crashes or if the power goes out BUT RSSOwlnix has a command line REPAIR function for the database!! This has saved my data more times than I can count. Then I switched to RSSOwlnix and I no longer have the lag issues while searching, and large database files of 2GB is no longer an issue either – as it is perfectly capable of handling extremely large database files without any performance and/or corruption issues. This was a huge inconvenience for me, because I essentially lost all my data. There is no function to repair the database built into the program that I know of, and I could find no information anywhere online on how to repair database via any other method (even on the user forums). Other than the search is extremely laggy/slow with a very large index > I learned that the program has a tendency for the database to corrupt when the database size gets around 2GB - also the database has a tendency to corrupt if (while the program is running) the computer crashes, power goes out (etc). Previously I tried to use QuiteRSS for the better part of about 1 year, and I have some miscellaneous complaints that others might consider if they have a lot of sites indexed which might generate a large database. FYI this many sites will produce a database size of around 4-6GB per year (depending on how much content is generated). I have around 800 sites indexed via RSS, and I export the database each year to archive each years feeds. This program, while discontinued, has been forked to RSSOwlnix which is under active development: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |