Configuring Buffalo LinkStation Live Email Notification For Gmail
I recently purchased a Buffalo LinkStation Live 1TB
(Official Buffalo Website) and noticed a feature which would notify me via email if the device experiences any failures.
This is great, as you wouldn't want 1TB of data crapping out on you. Without any early warning signs.
Following Gmails instruction on how to configure for other mail clients, I proceeded to configure my LinkStation.
Access Email Notification
On the top most tab, go to "System", then "Maintenance". You will be presented with an accordion menu for "Email Notification" and "Restart LinkStation". If "Email Notification" is not opened, click on it.
You should be presented your configuration options for the email notifications. Click on "Modify Settings".
Update Configuration
Configure your settings as follows:
- Notification: Enable
- SMTP Server Address: smtp.gmail.com
- SMTP Port No.: 465
- Authentication Type: LOGIN(SMTP-AUTH)
- SSL/TLS: SSL
- Username: your full email address (including
@gmail.comor@your_domain.com) - Password: your email password
- Subject: choose something descriptive, I used "LinkStation Status Report"
Note: "POP 3 Server ADDRESS" and "POP3 Port No." are disabled, and you cannot enter values for them.
Configure Recipients and Report
Now you have to configure which email addresses will receive the report. Enter an email address under "Recipient(s)" and then click "Add". Feel free to add as many as you want.
Note: It appears that recipients are not CCed, so other recipients would not be aware of who is receiving the report.
I decided to enable all the reports. Just to make sure I don't miss any failures.
See the field for "o'clock". That is the time of day you want the message sent to you.
Once you are done click "Save".
Send Test Message
You will be brought back to the main menu for "Maintenance". Likewise you will see "Send Test Message" enabled. Click on "Send Test Message".
Strangely a modal window will appear saying "Saving Data...", which is not representative of what action is being taken. No problem, just let it finish its job.
Note: If the progress bar repeatedly reloads, as in once its completed it starts again from the beginning, then there are problems with your configuration.
When done, the modal window will change to display "Message has being successfully sent." (Yes grammar mistake included).
The Test Message
Open up your mail client, and you should receive this message with the header "LinkStation StatusReport::Information":
Test Mail Message
This e-mail notice is to confirm LinkStation functionality.
The LinkStation can be configured using the following URL:
[LinkStationInformation]
LinkStationName
: LinkStation (LS-CHL-V2)
Time
: 2010/03/07 11:28:32
Setting Screen
: http://192.168.1.2/
If you successfully receive this email, it means your email notifications are successfully working.
Actual Report
The actual report will be emailed to you with the subject "LinkStation Status Report:Activity Report":
Activity Report
[LinkStationInformation]
LinkStationName
: LinkStation
Time
: 2010/03/07 12:00:03
IP Address
: 192.168.1.2
Setting Screen
: http://192.168.1.2/
Running Time
: 13:31:14[HDD Usage Status]
Disk 1 Usage Rate
: 104500460 kbytes / 961618816 kbytes (Usage Rate
11%)[DISK error status]
DISK1 0
Well thats all! Enjoy your Buffalo LinkStation Live 1TB.
Twitter Weekly Updates for 2010-02-28
- @hakimism sends out a missing thumbdrive cap report to the @urekalabs (company) wide email #
- welcome @AimanNubailah to the @urekalabs team! #
- @razlanshah should setup out own boy band called urekaboys, heres looking at you @cenioraz @nicholasnuing @hakimism @ronshah @urekalabs in reply to razlanshah #
- Thinking of Usng the Ruby Gem rvideo? Its not maintained and doesn't work with latest ffmpeg (v0.5). Use fork on GitHub http://ow.ly/19KJb #
- @scy_krylief what are you talking about? they are a whole world of fun in reply to scy_krylief #
- @hazrilaizad yup she knows him, how do you know him? in reply to hazrilaizad #
- @ronshah legally? did you speed? cut traffic? drive on the emergency lanes? in reply to ronshah #
- @razlanshah you forgot us is it? @nicholasnuing @hakimism @Qishin @cenioraz in reply to razlanshah #
- @razlanshah i see where your priorities lie, naturally the girl first in reply to razlanshah #
- @hazrilaizad small world
in reply to hazrilaizad # - @blogjunkie busy, got you back in reply to blogjunkie #
- @hakimism ah, using "bikeshed problem" now
in reply to hakimism # - @suanie was he trying to impress a girl, or a guy? in reply to suanie #
- @AimanNubailah but tonights going to be a good night, tonights going to be a good good night in reply to AimanNubailah #
- training @nicholasnuing to be a rails guru #
- @hakimism is jealous @syedfarouq is kacau-ing @AimanNubailah #
- @kegan yup was able to change? having problems with yours? in reply to kegan #
- its raining cats and dogs here at @urekalabs #
- @kegan need to leave machine there, unless you try going to the apple service center in section14. deal directly with the people who fix it in reply to kegan #
- good start of the day, had a good programmer interview here at @urekalabs #
- power is out at the island on @urekalabs #
- @r0kawa you ada qualifcations? in reply to r0kawa #
- I just restored power at @urekalabs #
- @syedfarouq you want to learn how to ride those humps eh? in reply to syedfarouq #
- kak @surianee made me a milo! #
- we have girls joining the urekaboys club #
- wip at @urekalabs with @hakimism @razlanshah @nicholasnuing @AimanNubailah @syedfarouq @matinfayzal @surianee #
- @razlanshah is giving everyone a word of advice in the @urekalabs wip #
- @nicholasnuing is confirmed for @urekalabs, no more probation for you dude! congrats #
- @ronshah is here for the @urekalabs wip #
- @hakimism's turn to talk at the @urekalabs wip #
- man, missing the lion dance because of the @urekalabs wip #
- @AimanNubailah has introduced a spy into the @urekalabs meeting #
- @razlanshah I feel it was hectic. Needs more control. in reply to razlanshah #
- @hakimism didn't get anything in reply to hakimism #
- @razlanshah oi, i'm the only one allowed to have the booming voice in reply to razlanshah #
- I passed by a store called "flying corpses", blinked and then realized it was calling "flying carpets" #
- @Ngeow apologies, something came up and was unable to make it, whens the next round? in reply to Ngeow #
- TM Representative told me TTDI is getting High Speed Broadband (HSBB) by 29th March. fibre to the home baby. #
- @Ngeow any plans to host an event? in reply to Ngeow #
- @munirah_ congratulations! when is it due? in reply to munirah_ #
MacPorts lame: output buffer too small
I've run into a small problem working with MacPorts ffmpeg port.
Trying to convert a file I get the error:
lame: output buffer too small
Now this isn't a problem with ffmpeg, but more specifically the MacPorts lame port.
As of today, the latest version of lame in MacPorts is v3.98.2. I needed to easily rollback to a previous version of lame, one which worked.
I scoured the MacPorts for the previous version of the lame Portfile. I found one for lame v3.98.0, and decided to give it a try.
Installing Older Port
Inside the command line I had to enter the following:
svn checkout -r 39480 http://svn.macports.org/repository/macports/trunk/dports/audio/lame
This would checkout the revision of lame I wanted. I entered the directory and executed:
cd lame sudo port install
After installation, I gave it a try and everything worked!
Prevent lame From Being Upgraded
Now if you generally update your MacPorts via port upgrade outdated or port -u upgrade, you'll have to becareful.
Running those two commands will upgrade your lame to the current revision, which may break your setup again.
Instead you are required to upgrade your MacPorts like so:
sudo port upgrade outdated and not lame
There you have it! Hope you enjoy your lame!





