It would be really nice…

It would be really nice to have fully integrated DTrace into Linus tree. Hopefully, it will happen soon.

OpenIndiana Hipster 2017.10 Released with…

OpenIndiana Hipster 2017.10 Released with Latest X.Org Server, MATE 1.18 Desktop

OpenZFS Developer Summit 2017 live.

Zabbix 3.4.3 has been released

As usually many bug fixes
Just done upgrade to 3.4.3 on my lapto by rebuilding my rpm packages using oneliner:

$ cd ~/rpmbuild/SPECS; sed -i 's/\(Version:.\( *\|\t*\)\)\(.*\)/\13.4.3/' zabbix.spec; wget -P ../SOURCES $(rpmbuild -bp --define "prep %dump" zabbix.spec 2>&1 | awk '/SOURCEURL0/ {print $3}'); rpmbuild -ba --quiet zabbix.spec; sudo rpm -Fvh ../RPMS/x86_64/zabbix**

My first Fedora package maintenance

Few months ago I’ve applied for packager permission on my Fedora developer account and after passing process taking over xml-security-c package which quite long not been well maintained I’ve started my work.

Today after many small issues (not everything is well explained in Fedora documentation) I’ve managed first time finish committing all my changes to Fedora git repository and push build xml-security-c for rawhide and f27 branch.

Summary list of changes in new xml-security-c release and some fedpkg output:

* Wed Aug 30 2017 Tomasz Kłoczko – 1.7.3-2
  • added patch which allows build xml-security-c against openssl 1.1
  • added ac_fixes patch: do not use sed to remove hardcoded compile options. Use patch because you will never know is such correction still needed (added autoconf, automake and libtool to BuildRequires)
  • added libstdc++-devel to BuildReqires and to devel Requires
  • add explicit all %%configure options to prevent build by mistake package against nss and force use openssl
  • added –disable-debug to %%configure options
  • added use %%autosetup in %%prep
  • do not waste IOs on remove not packaged files and add them %%files with %%exclude
  • indent and clean spec (move patch comments to the patch)

Continue reading

My zabbix patches for zabbix 3.2.7

If someone quite often is spending a time on creating new templates quite important is to use the same set of settings for all items or graphs. As well few default web frontend settings are not IMO so useful as they can be in large sale monitoring so when I’m building my own rpm packages I’m few my patches to change some settings.

I’ve decided to publish few my patches which I’m updating since probably zabbix 1.8. Attached archive is for latest zabbix 3.2.

In attached tar.gz file are patches:

  1. zabbix-default-200_lines_in_dashboard.patch
    • chage in default length of latest alarms from default 20 to 200.
  2. zabbix-default-create_graph_with_axe_on_righ_side.patch
    • create new graph with default vertical axe always on right side
  3. zabbix-default-creatchage e_graph_with_default_all_func.patch
    • create new graph with “all” function to show on trends graphs min/max band with avg line instead only avg
  4. zabbix-default-frontend-php.patch
    • change ZBX_PERIOD_DEFAULT from 1h to 3h so any first time seen graph will be offered in 3h time scale instead 1h
  5. zabbix-default-graph_900x400.patch
    • change newely created graph default resolution to 900×400
  6. zabbix-default-history_15d.patch
    • newely created item will have hard coded 15d raw history data ifg globally if this value is not overwritten by zabbix server settings to ignore all items history length and used global one
  7. zabbix-default-item_type_zabbix_item_active.patch
    • crate new item as zabix active
  8. zabbix-default-SNMP_comunity.patch
    • in SNMP new item use as SNMP community {$SNMP_COMUNITY} instead hardcoded “public” and offer blank OID instead interfaces.ifTable.ifEntry.ifInOctets.1.
  9. zabbix-default-proxy_ZBX_MAX_HRECORDS_50000.patch
    • increase max size of the proxy batch of the monitoring data from default 1000 to 50000

Most of those patches are correcting/adjusting personal preferences so they are not worth to push to zabbix however it would better to have possibility to change those settings over Administration->General instead fiddling in php zabbix application code.
Probably only default-SNMP_comunity patch is worth to push it to regular zabbix code.
proxy_ZBX_MAX_HRECORDS_50000 patch has been published here by me few times and hopefully zabbix dev team will allow tune ZBX_MAX_HRECORDS over proxy configuration setting not forcing to recompile binaries.

archive with all those patches is included in attachment of the post on zabbix patch forum