This is not a typo. We actually have a significant new ISO in the works on the heels of the 7.3.0 release. These updates are already in updates-testing and you can follow the usual procedures to update to update to these patches once Peter has uploaded them to his QA servers. Or if you have test-only boxes that can tolerate volatile RPMs [ie. has snapshots], you can enable the updates testing repo and get a look. We plan on pushing this update quite soon to the community so please test it early if you can and let us know if you see any problems.
The two primary features on this update are:
* Localization into 80+ languages
* Proxy settings capability for external facing NICs for ClearOS behind proxy servers
I've already made a test ISO and you can now download it from here:
http://mirror.clearos.com/clearos/testing/7/iso/x86_64/
The two primary features on this update are:
* Localization into 80+ languages
* Proxy settings capability for external facing NICs for ClearOS behind proxy servers
I've already made a test ISO and you can now download it from here:
http://mirror.clearos.com/clearos/testing/7/iso/x86_64/
Share this post:
Responses (6)
-
Accepted Answer
Yes, that should be correct. The ISO that is tagged officially as 7.3.1 will be the quarterly roll up that should happen at the beginning of Q2. We are transitioning into a long term model where the ISO is released with all the rollup updates each quarter since the install is always that same and updates can merely be applied. It makes sense to do it this way because our ISO is merely a reflection of what is in verified updates as opposed to the community release packages. This is done so that whether you are community, home, or business, you get the better quality packages on the ISO...always. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
actually in radius you need to modify /etc/systemd/system/multi-user.target.wants/radiusd.service , so it looks like
[Unit]
Description=FreeRADIUS high performance RADIUS server.
After=syslog.target network.target
After=slapd.service
[Service]
Type=forking
PIDFile=/var/run/radiusd/radiusd.pid
ExecStartPre=-/bin/chown -R radiusd.radiusd /var/run/radiusd
ExecStartPre=/usr/sbin/radiusd -C
ExecStart=/usr/sbin/radiusd -d /etc/raddb
ExecReload=/usr/sbin/radiusd -C
ExecReload=/bin/kill -HUP $MAINPID
[Install]
WantedBy=multi-user.target
so now Radius actually start at boot -
Accepted Answer
) 
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »