tresni / freenas-rss-extension

Automatically exported from code.google.com/p/freenas-rss-extension
0 stars 0 forks source link

Errors Flooding Log in FreeNAS .7 #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. FreeNAS .7
2. RSS Extension
3. rss_cron.php 

What do you see instead?

"Warning messages" flooding the error log because config changes cause this
to happen in FreeNAS .7... since the rss_cron.php writes to the config file
every time it runs, it causes these warning messages to be written to the
error log (very distracting) every 15 minutes (or whenever the cron job is
scheduled for)

What version of the product are you using? On what operating system?

Latest RSS Extension and FreeNAS .7 (any version, but I am using latest
nightly)

Please provide any additional information below.

Follow this link for more detail in my thread on the FreeNAS forums :
https://sourceforge.net/apps/phpbb/freenas/viewtopic.php?f=78&t=3975

Original issue reported on code.google.com by BMcClure937 on 29 Sep 2009 at 2:27

GoogleCodeExporter commented 9 years ago
The write_config() in rss_cron.php is the offending line, but it's required 
when there 
are changes to things stored in the configuration file (just smart episode 
filtering 
now I think.)  I'll see if I can update this so it only writes changes if there 
were 
changes, will at least reduce the number of messages you see, but it won't get 
rid of 
them (nothing I can do about that it appears.)  I'll look at moving more than 
just 
history out of the config.xml and into a settings file.

Original comment by tre...@gmail.com on 29 Sep 2009 at 3:19

GoogleCodeExporter commented 9 years ago
I know that this is the offending line ;) 

I took a look at the code and understand that the "write_config()" line is the
problem. I just wanted to bring this to your attention so we can work to 
minimize
this and possibly migrate things from being stored in the config to a 
proprietary
file that is used with the extension. 

Also, with the upcoming possibility that you mentioned about the "Transmission
Extended Setting Extension"... this may be a good idea to begin migrating 
anyhow so
that the extension can have a unified filed for the configuration (and not use 
the
config.xml for FreeNAS). 

Original comment by BMcClure937 on 29 Sep 2009 at 3:23

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r60.

Original comment by tre...@gmail.com on 22 Oct 2009 at 1:19