Hi,
from my previous post I learned that zoneminder doesn't work with hw compression cards (anyways hw compression cards manufacturers such as hikvision, are developing linux drivers....it would be interesting to adapt these cards to zoneminder, since they do motion detection in hw....).
Since it's a requirement for me using zoneminder, I'm thinking to buy a card such as PV-149 and a stronger hw. what do you suggest?
Reading the forum I found people saying that a dual core 2 P4 1.8Ghz is enough: do you agree?
Is zoneminder able to use the parallelism feature provided by a multicore cpu?
many thanks,
Paolo
4 analog cameras + pv-149 + required hw
load
You can also reduce CPU load for lower-powered systems a lot by just disabling services that you don't need running. Stuff like bluetooth, hald, and ACPI that you do not need (normally, in a server you intend to run 24/7 and have it constantly checking for hardware changes).
Though these seem like they would be low on CPU usage, I reduced my load on a Duron 1.6 from .8 to about .25-.3 by shutting off stuff I didn't need. Also, it you have no need to be directly on the console with it, you should consider changing your default run-level from 5 to 3, as there is no need for X to run locally for it. This saves a lot of resources.
Though these seem like they would be low on CPU usage, I reduced my load on a Duron 1.6 from .8 to about .25-.3 by shutting off stuff I didn't need. Also, it you have no need to be directly on the console with it, you should consider changing your default run-level from 5 to 3, as there is no need for X to run locally for it. This saves a lot of resources.
Re: load
Be careful with advice about runlevels. In the "olden" days with Red Hat and Fedora, runlevel 5 included the GUI login screen. For a server, you'd want runlevel 3, a console only login. However, Debian based systems like Ubuntu/Kubuntu have a different setup. And from my understanding, this is where more Linux flavors are headed (as debatable as this is). A Debian system's default runlevel is 2. The rest, 3-5, don't default to a console only login. Runlevel 1 is the "emergency, single user, no services" bootup.darkpaw wrote:You can also reduce CPU load for lower-powered systems a lot by just disabling services that you don't need running. Stuff like bluetooth, hald, and ACPI that you do not need (normally, in a server you intend to run 24/7 and have it constantly checking for hardware changes).
Though these seem like they would be low on CPU usage, I reduced my load on a Duron 1.6 from .8 to about .25-.3 by shutting off stuff I didn't need. Also, it you have no need to be directly on the console with it, you should consider changing your default run-level from 5 to 3, as there is no need for X to run locally for it. This saves a lot of resources.
More importantly, just do a regular server install to begin with. No GUI, no unnecessary services, etc. You'll be way ahead.
Lee's advice is the preferable route to take if you're a Linux novice. On any server I'm building I never install the GDM or KDM GUI tools. However, when I was first starting in Linux I'd install the GUI even on servers. That way if there was something I couldn't figure out on the command line, I could revert back to the GUI environment.Lee Sharp wrote:In Ubuntu, just Disable GDM from the services tool. Now it will start in text mode, but you can have a gui with 'startx' at any time. You also still have all the gui tools via ssh without the overhead of running x on the server.
Fedora
If you have the UI installed, but are running at run-level 3 in Fedora (CLI only), all you need to do to get the UI up is type: init 5
I can't speak about Debian-based distros like Ubuntu, because I don't like them. But for RedHat-based versions like Fedora, this is definitely the way to go for ease of use and CPU load.
I can't speak about Debian-based distros like Ubuntu, because I don't like them. But for RedHat-based versions like Fedora, this is definitely the way to go for ease of use and CPU load.