Add zabbix include files and directories
Fix syntax error in software module
Skip by default cisco discovery protocol
Eliminate some volatile system data from snapshot
Hi Sven, Did you check "Why is my scc client hanging?" of the http://sysconfcollect.sourceforge.net/examples/scc-help/scc/FAQ.html? When there is no child process of the "deepest" scc-collect process, you could run "strace" on it to find out what it is doing. Or you could run scc-collect only. Please refer to the manual page for the required option. regards, Siem
Extend copyright to 2020
Extend copyright to 2020
Extend copyright to 2020
Add crypto-policies and ssh_config.d and sshd_config.d files
You can indeed delete the files and then run 'scc-update -f' to regenerate the summaries without the removed systems. You can also run 'scc-realm -d -L <comma_separated_systems>' to remove the systems and generate the summaries.</comma_separated_systems>
Add label option to assign (minimal) system via auto-realm-config.
Label of client is attribute for auto realm management
Add label to summary.data
Ignore logins for Solaris
Limit label to alpha-numeric
compression ratio is variable zpool data
Release of 1.26.73 of scc
Start new release.
Adopt FAQ and manual pages from release 1.26.73 of scc.
Release 1.26.73 of scc.
Finalize release scc 1.26.73
Add release notes
Change class of openvpn data from software to network
More defensive programming for java check
Ensure correct run of hp-ov tests
Ensure processing by test of perms module
Clarify difference between user and system modules and advice system modules (triggered by Keith Koene)
Mention additional examples of user modules (indicated by Bill Dietrich)
The processes are already in the snapshot (for example http://sysconfcollect.sourceforge.net/examples/scc.centos70.html#cfg_system_processes). You will only need the extra module when you want a specific classification of the running/absent process.
Please have a look at /opt/scc/bin/scc-plugin. This is a template for a new module. When you make your new module a system module, it will be invoked automatically whenever scc is used. User modules need to be specified. I will make this disctinction more clear in this file. The indicated file contains all variables and files that are in place when the module runs. In your case the ${PROC_FILE} file contains all running processes when scc started, so there is no need to do your own 'ps -ef | grep...
Please have a look at /opt/scc/bin/scc-plugin. This is a template for a new module. When you make your new module a system module, it will be invoked automatically whenever scc is used. User modules need to be specified. I will make this disctinction more clear in this file. The indicated file contains all variables and files that are in place when the module runs. In your case the ${PROC_FILE} file contains all running processed when scc started, so there is no need to do your own 'ps -ef | grep...
Add windscribe (requested by Bill Dietrich)
The reason is I made a note to ask you for the output of the widscribe status and firewall commands, but never sent it to you and forgot about this. Please PM me the output and I will add the command.
I will add a reference.
Hello Keith, The released rpm does not contain a README. I recently have been made aware and fixed that in the development version. For the time being, you can have a look at https://sourceforge.net/p/sysconfcollect/code/HEAD/tree/scc-srv/trunk/README. It contains a short description of scc-srv. The details of the configuration, setup and operation of scc-srv can be found in manual page scc-srv(5) (add /opt/scc-srv/man to $MANPATH). This should get you going. Please let me know when you need additional...
Hello Bill, Summarizing the emails we exchanged. Multiple updates have been done based upon your posts. First of all, a lot of implicit knowledge has been made more explicit. This will certainly help new users. The README file is now more generic, installed in the doc directory and mentioned in the post-install message. The README now also indicates the 'goal' of scc to assist in deciding in future extensions. The manual pages no longer contain remaining parts of escape sequences. The multiple use...
Add sftp interface to obtain scc-data from clients
Add 4MLinux installed addons and avoid starting the game pacman.
Add NixOS channels
Add Void Linux boot configuration
Add xbps packages for Void Linux
Indicate in pkg_files/README that scc-srv-install installs a non-packaged version of scc-srv (triggered by Bill Dietrich)
Indicate in pkg_files/README that scc-install installs a non-packaged version of scc (triggered by Bill Dietrich)
Issue warning when installing source after installing packaged version (triggered by Bill Dietrich)
Use test instead of [[ for NixOS to avoid errors with /bin/sh (reported by Bill Dietrich)
Fix typo
Add NixOS system specification and installed packages
Extend PATH for NixOS and ensure existence of transfer directory for source install
Create data directory itself instead of parent
With Realms Configured SCC Host Web Server presents Errors
Hello Jeff, Good to see the issues have been resolved. I will close this bug. regards, Siem
Set correct selinux context for multiple realms after upgrade
I reproduced both errors by creating a realm with a space in the name. I have extended the tests of both scc and scc-srv to report this error and then fixed both files and ran the tests without errors. I have uploaded new versions of scc and scc-srv. Please check whether the new versions solve your issues.
Handle realms with space in their name (reported by Jeff Wilkins)
Handle realms with space in their name (reported by Jeff Wilkins)
Could you please provide the SVN ID's of scc_0600_s_software and scc-summary? Does the name of one your realms contain a space?
Could you please provide the SVN ID's of scc_0600_s_software and scc-summary?
Minor updates in manual page of scc-pull
Ignore messages from checksec
Add protonvpn status (requested by Bill Dietrich)
Hello Jeff, Should have thought about that. The -O option now implies the -U option and creates and chowns the destination directory specified with the -s option. This reduces the number of steps in the manual page and makes the procedure more compact. Thank you for the hint. regards, Siem
Automate destination directory with scc-pull -O <owner> (indicated by Jeff Wilkins)
Facilitate additional processing of local home directories in user modules (indicated by Bill Dietrich).
Support non-root transfer for systems behind a firewall (requested by Jeff Wilkins).
Hello Jeff, Instead of changing the ownership of transfer/cp I created subdirectory transfer/cp/scc and changed the ownership of this directory. Furthermore the -O option has been added to scc-pull to specify the ownership of the files on the gateway host. The manual page scc-srv(5) now also contains the commands for this non-root transfer from client to gateway to presentation server. I have also documented how to manage the lists of client systems of the gateway server by the presentation server....
Avoid failed bats test and remove duplicate code
Fail on multiple use of -S and -e options (indicated by Bill Dietrich)
fix typo
Install README in doc (triggered by Bill Dietrich)
Install README in doc and indicate this file after install (triggered by Bill Dietrich)
Install README in doc and indicate this file after install and with -h options (triggered by Bill Dietrich)
Extend README (suggested by Bill Dietrich)
Extend README (suggested by Bill Dietrich)
Extend README (suggested by Bill Dietrich)
Eliminate escape-sequences from manual pages (reported by Bill Dietrich)
Eliminate escape-sequences from manual pages (reported by Bill Dietrich)
Eliminate escape-sequences from manual pages (reported by Bill Dietrich)
Hello Jeff, I have implemented this exact setup several years ago and you made me wonder how I did that. When I looked for the details, it appeared that the ownership of the transfer/cp directory is controlled/reset via puppet. The manual page (scc-srv.5) contains the root-only setup on the client-proxy-scc-srv chain. For a native non-root setup I need to eliminate the 'ownership' of this directory from the rpm. I will also add a complete non-root example in the manual page. I will post here when...
Ignore some more variable sysctl data
Clarify ignoring differences due to first run of user module
Use user-module data from previous run when not selected to run
Fix haproxy check for directory
essage=Several contributions from Bill Dietrich
Additional location of sudo on Solaris
Thank you for all suggestions and the contributed nodules. Please give some time to evaluate this. I would ike to suggest to discuss them via messages and then summarize in this forum.
The Bugs section was not yet configured. Should be ok now. I have restricted new tickets to authenticated users.
Hello Bill, Did you check the manual page of scc? The DESCRIPTION section contains a regular expression example of this option. On a shell prompt you have to add directory /opt/scc/man to your MANPATH environment variable. You can also check online at http://sysconfcollect.sourceforge.net/examples/scc-help/scc/scc.html. Most options of all scc and scc-srv scripts only use their last instance. I will check the manual pages to indicate this (and the exceptions). regards, Siem
Hello Bill, I was under the impression that I would receive alerts for posts in this forum, but unfortunately that is not the case. Otherwise I would have reacted much earlier. What instructions did you miss for your desktop system? Did you download the rpm from the website (http://sysconfcollect.sourceforge.net/download.html) and follow the instructions for the RPM? Or did you download the src.tar.gz and went from there? Your remark makes me realize that the README indeed only covers development...
Ensure presence of sysctl-data when running scc-collect in interactive mode
running services is now variable data to limit changes
Several additional files and commands
Additional jenkins xml files with mainly variable data
Improve determination of java path from process list and provide realpath
Determine java versions
Add haproxy configuration (suggested by Hendrik Visage)
Release of 1.19.44 of scc-srv
Release of 1.19.44 of scc-srv
Start new release.
Release 1.19.44 of scc-srv.
Finalize release scc-srv 1.19.44