Hi Nathan,
I just did a clean install of ESSG 4.1.2 just out of curiosity.
I installed the following via rpm -Uvh commands :-
libpcap-0.6.2-11.7.1.0.i386.rpm
openssl096-0.9.6-6.i386.rpm
openssl-0.9.6b-28.i386.rpm
openssl095a-0.9.5a-18.i386.rpm
ntop-2.1.2-0.i386.rpm
(note : all 3 openssl packages were installed on one rpm -Uvh command line)
Then, I created the /var/ntop directory.
I then started ntop using (choose your own parameters if you like):-
ntop -i eth0 -W 3000 -u admin
and supplied the admin password (followed by confirmation).
I used the admin accound as this was a clean install and did not have any other users on the system yet. Also, I am the first to admit that I do not know whether or not the openssl compatibility layer packages installed will break any existing packages required by E-Smith (being still fairly new to linux), so test it first before trying it on a production server. All I know is the compatibility layer packages addresses the depency issues from the older packages in 4.1.2 (like needing libcrypto.so.0 and so on) without needing to force installing the packages.
ntop appears to be working fine on my test installation of ESSG 4.1.2. I subscribe to the belief that being a server, it should not run anything more than it really should, therefore did not try to script it to run automatically upon bootup. I prefer to start it manually as and when I need to perform any diagnostics and monitoring. If you need it so start automatically, follow the relevant sections from Harro and Dillard's How-To.
Hope you find this useful (even if just for fun).
Cheers,
Kelvin