| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
- The Client now runs in background (added a trailing & at the end of the command that runs the client);
- Removed the delays in the script during the service stop;
- Fixed the "default max states" information when it is not defined explicitally in the advanced configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Improved the reception of data from LCDd. Now there's a cycle that run until there's no more data do receive. Before that there was the possibility of a buffer overflow in LCDd. The timeout of the receiving socket is 25ms.
- Optimized the number of commands sent to LCDd every cycle. Now it is sent only the half;
- Rewritten with better code the error handling;
- Increased to 3 the number of attempts the client performs to reconnect to LCDd in case of disconnection;
- Simplified the startup scripts. Now lcdproc_client.sh is not generated/run anymore, since the error handling is managed by the client;
- Changed the startup scripts to run both LCDd then the client as "nice" process;
- Capped the wait time between each client cycle to 5 seconds. It still is calculated as the refresh frequency * the number of screen activated, but now it's capped;
- Increased to 8000 chars the trunk of data received from LCDd;
- Improved the "service stop" script. Now it cycle until LCDd is definitely killed and works even if LCDd is hung;
- Added a "welcome" string on the panel at the LCDd startup;
Thanks,
Michele
|
| |
|
|
|
|
|
| |
- Better managed errors. Now the client resets the error counter every successful communication session with LCDproc (before was a global counter). The error counter is managed inside the client (lcdproc_client.php).
- Because of the above change, now the "client script" (lcdclient.sh) do not cycle anymore.
|
|
|
|
|
|
| |
- In the settings, "Enable LCDproc" becomes "Enable LCDproc at startup"
- Added "After Install Info" message
- Limited the client loop to three times. After three errors connecting to the LCDd service the client will end
|
| |
|
|
|
|
|
|
|
|
| |
has been solved in a different way
- Set the custom Keys and Menu section for the "sdelcd" driver
- Added the Blacklight setting. Now it is possible to optionally turn the blacklight on, off or (default) to leave it managed by the panel
- Added the "output led" support for the "CFontz633" driver. This is totally to test since my panel doesn't have any output led, worked almost blind
|
| |
|
|
|
|
|
|
| |
- Added in the com port selection: com1 (dev/cua0), com1 and com2 alternative (dev/cuau0 and dev/cuau1)
- Added com port speed selection (hope users won't make a mess)
- Added Contrast/Brightness/Offbrightness selection. If the setting from the user do not match the possibility of the driver the setting is just ignored.
|
|
|
|
| |
Added the driver "hd44780 fast" as alternative to the previous driver that had set some delays.
|
|
|
|
| |
stead of the functions defined by the first developer.
|
|
|
|
|
|
| |
This change solves also the problems during reinstall.
Thanks
Michele
|
|
|
|
| |
This solves a problem during reinstall and saving the settings while the service is running.
|
|
|
|
|
|
|
| |
- I managed in the code ALL the drivers available in the package. Consider that before this change only 12 drivers on 35 were supported. Now all the selectable panels are supposed to work, with the default configuration values. If someone has problems with the new added drivers please let me know
- I added the IN/OUT statistics for a selectable interface. For the selected interface IN and OUT bytes are shown
- In the summary (visible to the ones that have a 4 line display) I added, if the width of the panel is bigger than 16 rows, the frequency in percent currently used
- I reduced the CPU interval in the load calculation from 1s to 250ms. This because setting the refresh of the panel to 1 second was actually 2 seconts (1 to wait for the refresh, 1 to wait for the CPU calculation)
|
|
Include a full list of all the drivers available (default build).
This is a development version under test, it's not granted it works in all conditions.
Reference: http://redmine.pfsense.org/issues/1406
|