2.3 LCDPROC
-
LCDPROC is no longer showing up in available packages
Is it no longer being offered?
-
just found this aswell :-( i just got my new server setup and was sad :-(
-
There appears to be a work around see this link.https://forum.pfsense.org/index.php?topic=44034.525
I'm waiting to see if someone can roll it up in a pkg, if not then I will try. But first I need to do a bunch of learning.
-
I ended up making a custom package with an install script that I just upload and run the install.sh file to have LCDPROC, but I do not have a pretty web page in the webgui YET. You can manually change the LCDd.conf to match the settings you need. Give me a bit to tweak some final bugs and settings and if you guys need it Ill post it once I know it will do no harm or evil to the system.
I love 2.3 so far, especially the new bootstrap gui, i have no had any issues like the posts I see so far, lucky me i guess : )
-
I ended up making a custom package with an install script that I just upload and run the install.sh file to have LCDPROC, but I do not have a pretty web page in the webgui YET. You can manually change the LCDd.conf to match the settings you need. Give me a bit to tweak some final bugs and settings and if you guys need it Ill post it once I know it will do no harm or evil to the system.
Thanks you are the man or woman!
-
So I'm looking for this install script. Please share, thank you!
-
I think I understand enough to have a go at making a 2.3 ports package now. Is anyone else doing it?
I assume LCDproc-dev would be the best one to port as it's had a lot of extra functionality added - is there anything LCDproc provides that LCDproc-dev doesn't?
Is there any reason to keep maintaining two packages: LCDproc and LCDproc-dev? There's a hint in this commit log that two versions are no longer needed, but I don't know the original reason for dev. If the purpose was to add LCDProc v0.5.4 drivers then we don't need two packages anymore.
Answered my own question:
@mdima:I just updated LCDProc to 0.5.4. In order to not to interfer with the package currently in use, I created a LCDProc-dev package.
^^ As Michele created LCDproc-dev to add early support for LCDProc 0.5.4, and a pfsense 2.3 package would be using LCDProc 0.5.7, there's no need to keep maintaining two packages.
Edit: damn, to submit code you must agree to foot ESF's legal costs if some SCO-Linux wannabe starts a frivolous lawsuit - not sure my pay grade would justify covering that. It would have to languish as an unofficial LCDproc package.
-
Whats up w/ this package? Any help needed?
-
If people want something to play with, here's my start at a pfsense 2.3 package. It's still the old UI, no Bootstrap changes yet.
-
Compiled package: pfSense-pkg-LCDproc-0.9.15.txz
-
Edit: damn, to submit code you must agree to foot ESF's legal costs if some SCO-Linux wannabe starts a frivolous lawsuit - not sure my pay grade would justify covering that. It would have to languish as an unofficial LCDproc package.
Why? Both LCDproc and pfSense are opensource. As a novice IT person (none programmer) I was looking for ways to compile LCDproc with other drivers and there was basically very little information from LCDproc people. If you could do this for pfSense I'm sure a few people here will donate.
-
I've got the configuration UI using pfSense's new OO Forms framework, this will allow the configuration to be a bit more flexible and more advanced features to be added, but right now not much has changed besides it hiding some settings if your LCD driver doesn't use them.
Why? Both LCDproc and pfSense are opensource.
Yeah, it's open source, which is cool, and I'm likewise keeping everything I do available to others, but pfSense won't add anyone else's work into their releases/packagemanager unless you agree to pay legal costs if someone sues them over it (like SCO-Linux tried to do with unix/linux). So you don't get paid anything, but you take on extra legal risk, which rubs me the wrong way. I'm not sure whether to be principled - I can see why they do it, and I very much doubt they'd actually ask an innocent contributor to pay up, but the terms of the contract are broad and don't offer any protection to people who have done nothing wrong - only contributed what they legally had the right to etc.
-
Those who have installed the pfSense 2.2 lcdproc into 2.3: there's a pfSense 2.3 issue affecting APU, ALIX and others which causes lcdproc_client.php to fill the log file with divide by zero exceptions if any of your screens display the CPU speed or frequency.
if the command /sbin/sysctl -n dev.cpu.0.freq_levels works on your system then you're not affected. Otherwise, you can either get powerd working on your system, or patch lcdproc_client.php
-
In a vain attempt to make LCDproc as handy as the old N1 Vision, I've added 3 extra screens that can take advantage of 4 row displays.
The screen in the bottom picture is blurred because the LCD is scrolling the device names, but the list is basically identical to the list you see on pfSense's "Status / Traffic Graph" page. Converting LCDproc's config screens to use the new OO Forms framwork means the config can work the same as the Traffic Graph:
Links to the code and ports package are in an earlier message, though I don't think many people have 4-row displays. Everything I wanted from LCDproc is done now, so I don't have any more changes planned.
Edit: Have added a requested i386 port as well
-
Thanks for updating teh package BTW! Love it.
-
CARP screen does not work because of this:
https://redmine.pfsense.org/projects/pfsense/repository/revisions/2a5960b07bb2a40aeaf81423b0c52d5629e87e49
Fix /usr/local/pkg/lcdproc_client.php:
–- /root/lcdproc_client.php 2016-09-06 10:42:24.394680000 +0200
+++ /usr/local/pkg/lcdproc_client.php 2016-09-06 11:29:38.170118000 +0200
@@ -272,8 +272,7 @@
$netmask = $carp['subnet_bits'];
$vhid = $carp['vhid'];
$advskew = $carp['advskew'];- $carp_int = find_carp_interface($ipaddress);
- $status = get_carp_interface_status($carp_int);
- $status = get_carp_interface_status("_vip{$carp['uniqid']}");
switch ($status) {
case "MASTER":
$mastercount++;
-
Is there a working version compatible with 2.3.2- Release?
-
Just installed this in 2.3.2_1. Seems to work fine.
I'm not sure if the previous hard time limit on php processes still applies. You can always start the default client with Shellcmd instead as have always done previously. Or if the service start issues still exist in the SDEC driver.
Steve
-
Seems to start fine with the SDEC driver, with the php client at least.
-
If people want something to play with, here's my start at a pfsense 2.3 package. It's still the old UI, no Bootstrap changes yet.
-
Compiled package: pfSense-pkg-LCDproc-0.9.15.txz
I followed these instructions but I can not get it to work on my x750e…. I probably inputted it in the wrong section but the config shows it and it does not list in the Installed PKGs screen.
-
If people want something to play with, here's my start at a pfsense 2.3 package. It's still the old UI, no Bootstrap changes yet.
-
Compiled package: pfSense-pkg-LCDproc-0.9.15.txz
I followed these instructions but I can not get it to work on my x750e…. I probably inputted it in the wrong section but the config shows it and it does not list in the Installed PKGs screen.
It will not show up in the installed packages section, as it is not installed that way.
If you can see it on the services screen it is fine.
Once you see it on the services menu enable the service and save. Next go back in and enable the screens you require, and save again. finally start the service from the services menu in diagnostics.
I have found that is is not necessary to manually edit the package file any more, if you do you may end up with two entries for LCDproc.
