Hi folks. I finally took the plunge and updated to v6. It went without a hickup and so far so good. Now for some questions hopefully someone can answer or lead me to the right place.

 

First, in 5.0.5 in Email settings there were a few extra email settings that don't seem to be in v6, mainly the temperature settings and critical command. Are these no longer available/needed? Also, what about the "append status to subject" option?

 

Next, I only had a few things running in my setup:

 

Dynamix (no longer needed)

apcupsd (no longer needed)

powerdown (already installed new one)

cache_dirs (already installed new one)

BTSync (overbyrn's version)

unmenu (although I have no idea what from that I actually was using anymore. once I installed Dynamix I moved away from that as much as I could.)

 

So what I'm trying to determine right now is the best way to install BTSync. I know everyone is saying if you're going to install anything it should be in a Docker, but I'm wondering if that might be overkill for it. Yes or no?

 

Along with that question, no matter which option I choose, will I be able to use the existing configuration directory I had for the old plugin which resides on my cache drive? Or am I just going to have to reconfigure the whole thing?

 

I may well move off BTSync, but it's already running fine for me so I'm not sure I want to rock the boat and move to something else right now.

 

Last question is about Mover. In my old setup I had created a custom mover file that dump caches before and after running Mover in order to combat the problem with ever growing memory usage. Is this type thing still needed or no? And if so, what's the new procedure to add this back into the Mover file (or is it the same as before)?

 

Thanks all!

First, in 5.0.5 in Email settings there were a few extra email settings that don't seem to be in v6, mainly the temperature settings and critical command. Are these no longer available/needed? Also, what about the "append status to subject" option?

Not an obvious place for them, but these are in the Display Settings. Also see Notification Settings for more options.

...Last question is about Mover. In my old setup I had created a custom mover file that dump caches before and after running Mover in order to combat the problem with ever growing memory usage. Is this type thing still needed or no? And if so, what's the new procedure to add this back into the Mover file (or is it the same as before)?

What is the "same as before" method you refer to? Something in go to replace built-in mover?

First, in 5.0.5 in Email settings there were a few extra email settings that don't seem to be in v6, mainly the temperature settings and critical command. Are these no longer available/needed? Also, what about the "append status to subject" option?

Not an obvious place for them, but these are in the Display Settings. Also see Notification Settings for more options.

...Last question is about Mover. In my old setup I had created a custom mover file that dump caches before and after running Mover in order to combat the problem with ever growing memory usage. Is this type thing still needed or no? And if so, what's the new procedure to add this back into the Mover file (or is it the same as before)?

What is the "same as before" method you refer to? Something in go to replace built-in mover?

 

Thanks for the reply. I had found and modified the Display Settings for temp, but I wouldn't think that translated to email notifications the temp is reached/exceeded. Are you positive those are the same settings as what was in Email settings before? And I've found and changed the Notification settings as well, but those other settings aren't there either.

 

And yes, in my go script I had a command that removed the original mover file and replaced it with a new one in /boot/custom with this command:

 

rm /usr/local/sbin/mover

ln -s /boot/custom/mover /usr/local/sbin/mover

 

But as I stated, that memory issues may well have been just a v5 thing and now that we're 64bit maybe it's no longer an issue with cache_dirs. Honestly don't know, but I haven't seen anyone bring that up lately and I only made those modifications based on info gleaned from past posts on the issue.

Thanks for the reply. I had found and modified the Display Settings for temp, but I wouldn't think that translated to email notifications the temp is reached/exceeded. Are you positive those are the same settings as what was in Email settings before? And I've found and changed the Notification settings as well, but those other settings aren't there either.

 

And yes, in my go script I had a command that removed the original mover file and replaced it with a new one in /boot/custom with this command:

 

rm /usr/local/sbin/mover

ln -s /boot/custom/mover /usr/local/sbin/mover

 

But as I stated, that memory issues may well have been just a v5 thing and now that we're 64bit maybe it's no longer an issue with cache_dirs. Honestly don't know, but I haven't seen anyone bring that up lately and I only made those modifications based on info gleaned from past posts on the issue.

The warning or critical temperature settings trigger a warning or alert from the notifications page. Other things can also trigger notifications, such as the disk utilization settings.  This definitely has worked for me.

 

The notification events and the notification methods in v6 are much more than anything provided by v5 or unMenu.

 

In case you missed it, there is an Advanced View in Notification Settings (toggle in upper right).

 

Also, Notification Agents.

 

As for mover and memory, how much memory do you have? Try it without the modification.

... I had found and modified the Display Settings for temp, but I wouldn't think that translated to email notifications the temp is reached/exceeded. Are you positive those are the same settings as what was in Email settings before? And I've found and changed the Notification settings as well, but those other settings aren't there either.

 

Yes, warning and critical temperatures have moved under display settings. And appropriate notifications are generated when these thresholds exceed.

 

In v6 the notification system has been completely revised/revamped and does a lot more than what was available under v5.

 

There are three classifications notice, warning and alert and this replaces the single status notation under v5. Also there is a choice to send notifications by email, to browser or to one or more (mobile) agents. Each type of notification can be set to use none or all of these methods to notify the user. Together with various status update notifications. Try different settings to see what is most suitable to your needs.

 

 

 

The warning or critical temperature settings trigger a warning or alert from the notifications page. Other things can also trigger notifications, such as the disk utilization settings.  This definitely has worked for me.

 

The notification events and the notification methods in v6 are much more than anything provided by v5 or unMenu.

 

In case you missed it, there is an Advanced View in Notification Settings (toggle in upper right).

 

Also, Notification Agents.

 

As for mover and memory, how much memory do you have? Try it without the modification.

 

I have 16GB. The problem before was that the memory wasn't freeing up or something and would appear full (real or imaginary I don't know) and dumping the caches after running mover was the key to keeping that in check. And yes, I'll run it stock for now to see how it behaves since something tells me this isn't a problem in the new version. I just wanted to pose the question for anyone that might know definitively on that.

Yes, warning and critical temperatures have moved under display settings. And appropriate notifications are generated when these thresholds exceed.

 

In v6 the notification system has been completely revised/revamped and does a lot more than what was available under v5.

 

There are three classifications notice, warning and alert and this replaces the single status notation under v5. Also there is a choice to send notifications by email, to browser or to one or more (mobile) agents. Each type of notification can be set to use none or all of these methods to notify the user. Together with various status update notifications. Try different settings to see what is most suitable to your needs.

 

Thanks for the confirmation on that!

I have 16GB. The problem before was that the memory wasn't freeing up or something and would appear full (real or imaginary I don't know) and dumping the caches after running mover was the key to keeping that in check. And yes, I'll run it stock for now to see how it behaves since something tells me this isn't a problem in the new version. I just wanted to pose the question for anyone that might know definitively on that.

Are you aware of this website?

 

I have 16GB. The problem before was that the memory wasn't freeing up or something and would appear full (real or imaginary I don't know) and dumping the caches after running mover was the key to keeping that in check. And yes, I'll run it stock for now to see how it behaves since something tells me this isn't a problem in the new version. I just wanted to pose the question for anyone that might know definitively on that.

Are you aware of this website?

 

Not that particular one, but the premise, yes. Again, I found the info here about the particular issue and proceeded with info I read. Was it 100% necessary? Maybe not.

I have 16GB. The problem before was that the memory wasn't freeing up or something and would appear full (real or imaginary I don't know) and dumping the caches after running mover was the key to keeping that in check. And yes, I'll run it stock for now to see how it behaves since something tells me this isn't a problem in the new version. I just wanted to pose the question for anyone that might know definitively on that.

Are you aware of this website?

 

Just an FYI - the memory issue I had on 5.0.5 isn't present in 6. It's behaving as I would expect at this point.