The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Re: Smart Meter on trial (BBC Video)



I've also drifted into that way of working. I put up a Synology DS207+
NAS server (7W in standby) which runs shared storage, web server,
connection to my CH CAN bus and other stuff I can't remember at the
moment. It's predecessor, a power hungry server now only comes on to
record/play MythTV, to do housekeeping on Economy 7 rate and when I want
a native Ubuntu computer.

Pete

dermot_bradley wrote:
> --- In ukha_d@xxxxxxx, "Paul Bendall" <paul@...>
wrote:
>
>> I'm coming to the conclusion that you need two Node1 servers (if
>> that makes sense) 1 very low power that is all 24/7 and another
>> high powered that only comes on for CPU intensive tasks, i.e web-
>> serving, ripping CDs /DVDs / Blu-Ray disks and streaming. The low
>> power one can control the high powered with WoL and CLI shutdown /
>> hibernate.
>>
>
> Agreed, that's the way I've been heading, although in my case I didn't
> think (at the time) the Mini-ITX route was the best way to go for
> cost-related reasons (mini-ITX parts tend to cost more) so went for a
> "mainstream" m-ATX motherboard with a low power Sempron in
it and when
> properly set up with Cool'n'Quiet etc its power usage won't be that
high.
>
> The 7x24 box will run Asterisk, MYSQL (for MythTV), 1-wire data
> collection, record power  meter data, handle incoming email, etc, and
> the rest will be done by the other box via WOL like you said.
>
>
>
> ------------------------------------
>
>
>
>
>


[Non-text portions of this message have been removed]


------------------------------------


UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.