sed -i 's/de.archive.ubuntu.com/ftp.uni-stuttgart.de/g' /etc/apt/sources.list /etc/apt/sources.list.d/* && sed -i 's/archive.ubuntu.com/ftp.uni-stuttgart.de/g' /etc/apt/sources.list /etc/apt/sources.list.d/* && sed -i 's/security.ubuntu.com/ftp.uni-stuttgart.de/g' /etc/apt/sources.list /etc/apt/sources.list.d/*
geometry=1900x1080 | |
#geometry=+1980+1 | |
# Uses GPU-accelerated video output by default. | |
vo=gpu-next | |
# Can cause performance problems with some GPU drivers and GPUs. | |
profile=gpu-hq | |
# ===== REMOVE THE ABOVE FOUR LINES AND RESAVE IF YOU ENCOUNTER PLAYBACK ISSUES AFTER ===== |
curl -X PUT -H 'Content-Type: application/json' -d '{ "index": { "refresh_interval": "30s" } }' http://$(hostname -f):9200/_settings
Whether or not to fsync and commit the translog after every index, delete, update, or bulk request. Increased risk of data loss if elasticsearch crashes
curl -X PUT -H 'Content-Type: application/json' -d '{ "index": { "translog.durability": "async" } }' http://$(hostname -f):9200/_settings
- Added support for r10k-like purge behaviour of stale content
Starting with v.0.7.0 g10k supports the r10k-like purge behaviour of stale content with the different configuration settings purge_level
and purge_whitelist
as documented here for purge_levels and here for purge_whiltelist
Please check if you need to whitelist files/folders inside your Puppet environments!
As an additional setting, you can also whitelist Puppet environments with deployment_purge_whitelist
, that would've been purged by the deployment purge_level
.
This can be helpful if you have a similar source name or prefix set. E.g. having a source called foobar
and
https://github.com/theforeman/foreman_api
d = ForemanApi::Resources::ConfigTemplate.new(
{
:base_url => $logindata[:foreman][:host],
:username => $logindata[:foreman][:username],
:password => $logindata[:foreman][:password],
})
data = d.index(headers={:page => 1, :per_page => 9000})
Using EJBCA community edition 6.5.0.5 with WildFly 10 and Java 8:
[...]
<subsystem xmlns="urn:jboss:domain:remoting:3.0">
<endpoint/>
<connector name="legacy-remoting-connector" socket-binding="legacy-remoting" security-realm="ApplicationRealm">
<properties>
<property name="org.xnio.Options.SSL_STARTTLS" value="false"/>
</properties>
object CheckCommand "check_tcp_wild" {
import "ipv4-or-ipv6"
command = [ PluginDir + "/check_tcp " + "$tcp_args$" ]
vars.tcp_args = "$tcp_args$"
}
we want to send certificate approval requests with different EEPs to different RA admin email addresses. Currently EJBCA only supports one email address for this under system configuration.
To configure the different RA admins mailing addresses we are using system properties in the JBoss configuration XML:
Resolving dependencies... | |
Installing rake (10.5.0) | |
Installing i18n (0.7.0) | |
Installing json (1.8.3) | |
Installing minitest (5.1.0) | |
Installing thread_safe (0.3.5) | |
Installing tzinfo (1.2.2) | |
Installing activesupport (4.1.14.2) | |
Installing builder (3.2.2) | |
Installing erubis (2.7.0) |
2016-04-12T14:08:16 [app] [I] processing report for foobar.domain.tld | |
2016-04-12T14:08:16 [app] [W] Action failed | |
| NoMethodError: undefined method `type_changed?' for #<ConfigReport:0x00000009f26198 | |
| /usr/share/foreman/vendor/ruby/2.1.0/gems/activemodel-4.1.14.2/lib/active_model/attribute_methods.rb:435:in `method_missing' | |
| /usr/share/foreman/vendor/ruby/2.1.0/gems/activerecord-4.1.14.2/lib/active_record/attribute_methods.rb:213:in `method_missing' | |
| /usr/share/foreman/app/models/concerns/foreman/sti.rb:27:in `save_with_type' | |
| /usr/share/foreman/app/services/report_importer.rb:129:in `create_report_and_logs' | |
| /usr/share/foreman/app/services/config_report_importer.rb:13:in `create_report_and_logs' | |
| /usr/share/foreman/app/services/report_importer.rb:40:in `import' | |
| /usr/share/foreman/app/services/report_importer.rb:20:in `import' |