SynoCommunity is glad to announce its new repo

[scoupy]

Why did you edited the crontab ? There is no reason to, and this is why the status is wrong in package center

For the users, it is weird, did you check the /etc/passwd ?

And for the shutdown, this is not really due to package, but the programs itself. It seems it is preventing umount of /volume1, since it's in use by the programs
You must create a shutdown script, and put it in the shutdown sequence folder
(but this is also weird, since normal shutdown does not prevent umount ...)

I edited CRONTAB because I was told to do so I have to admit that I barely know how to use ssh and I have clearly no idea how to do a script... Could you tell me the difference? Or at least why editing CRONTAB was a bad idea (since it works)?

Here is what I did:

Code: Select all

15      9       *       *       *       root    /bin/sh /var/packages/sabnzbd/scripts/start-stop-status start
30      9       *       *       *       root    /bin/sh /var/packages/sickbeard/scripts/start-stop-status start
25      9       *       *       *       root    /bin/sh /var/packages/couchpotatoserver/scripts/start-stop-status start
30      21      *       *       *       root    /bin/sh /var/packages/couchpotatoserver/scripts/start-stop-status stop
30      11      *       *       *       root    /bin/sh /var/packages/sickbeard/scripts/start-stop-status stop
30      23      *       *       *       root    /bin/sh /var/packages/sabnzbd/scripts/start-stop-status stop

I check on google and found this about scripts. Is it was I am supposed to do? I checked the code and I don't see where I should put the time I want them to start/stop...

[url]http://www.[Please control your language].com/2011/07/synology-startstop-init-d-scripts-for-sabnzbd-sickbeard-and-couchpotato/
[/url]

(replace control your language by checkthiss**tout.com where **=hi)

Regarding the /etc/passwd issue. Everything looks fine I think:

Code: Select all

couchpotatoserver:x:101:100:CouchPotato Server User:/usr/local/couchpotatoserver/var:/bin/sh
sabnzbd:x:100:100:SABnzbd User:/usr/local/sabnzbd/var:/bin/sh
sickbeard:x:102:100:SickBeard User:/usr/local/sickbeard/var:/bin/sh

Seb

[bud77]

This sound like your DSM session has expired, but your browser is using its cache

Try to refresh the page without using cache (CTRL + F5)

[bud77]

There is no need to add in crontab, there is scripts doing it automatically (at startup/shutdown)

Just remove the lines in crontab, and check if you still have issues (all might be related)

[scoupy]

I see but where can I find the scripts you mention? And how can I set a timer for SAB/CP/SB?

The only thing I saw is in SAB where I can add a shutdown command but no start command.

[bud77]

The scripts are the one you added in your crontab.

But there is no need to launch (or stop) them manually, since it will be done automatically after power on or shutdown

[scoupy]

Alright, I get your point but I am not sure you get what I want to do. I want SAB/CP/SB to start at a particular time and stop at a particular time, which are not the same than my NAS.

My NAS boots up at 9am and shuts down at 0:00am while I want the 3 apps to start somewhere around 9:30am and shut down at 11am.

Is it possible to do that without CRONTAB?

Thx,

Seb

[bud77]

I now understand your need. Crontab is the only way to do this, but it's not a normal behavior, so, expect side effects ... (still I don't understand why you don"t start the progz with the nas)

On a sidenote, are you aware you are reducing your hard drives life by proceeding this way ? You are increasing pretty much the "head parking"

[scoupy]

Back in the days (I don't know if it is still the case), Sickbeard was checking every X minutes if it had to do something. Thus, preventing the HDD to hibernate, even if Sickbeard had nothing to do since it was writting a line in the log...

I agree that for SAB and Couch it is not particularly useful... But I am not sure it increases head parking that much if I use my CRONTAB settings (it wakes up the HDD only once more than usual, right?).

[bud77]

Hibernate is even worse than stop/start. Yes, only once more, but thats 365 times a year ...

And you can manually set the timer for sickbeard, mine is set to every 8 hours for instance

[Kermode]

@Kermode : As stated in the post you opened, there is a filter based on user-agent, which is made from synology model + firmware.

Yes, I know.

This way, you can't download a package which is not specifically made for your own syno

So, you think people are advanced enough to install linux drivers, but won't allow them to look at a website because they are too stupid for that.

[bud77]

So, you think people are advanced enough to install linux drivers

Where do WE (SynoCommunity) tell anyone to install drivers ?

If you are talking about TVheadend, the problem is TVheadend itself. Just a quick reminder, we are only packaging programs, and make sure they works with synos

But in any case, feel free to uninstall all of our packages, I promise, we won't get pissed. Then you can enjoy your syno ... the way you like it ...

[Kermode]

If you are talking about TVheadend, the problem is TVheadend itself. Just a quick reminder, we are only packaging programs, and make sure they works with synos

To an audience you expect can install drivers but are too stupid to download the right material. Got it.

[noseboy]

Christ, if it bothers you that much then use a different repo.

[Kermode]

Christ, if it bothers you that much then use a different repo.

I was just responding to comments made. If it bothers you that much then don't comment

[bud77]

If you are talking about TVheadend, the problem is TVheadend itself. Just a quick reminder, we are only packaging programs, and make sure they works with synos

To an audience you expect can install drivers but are too stupid to download the right material. Got it.

If it is as easy as "download drivers" why don't you do it by yourself ?

Just buy a compatible usb stick, and stop crying for specific drivers ...