We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now the following code in internal/module/registerlayer.pp class creates layers.conf file as root.
layers.conf
exec { "jboss::module::layer::${layer}": command => "/bin/awk -F'=' 'BEGIN {ins = 0} /^layers=/ { ins = ins + 1; print \$1=${layer},\$2 } END {if(ins == 0) print \"layers=${layer},base\"}' > ${jboss::home}/modules/layers.conf", unless => "/bin/egrep -e '^layers=.*${layer}.*' ${jboss::home}/modules/layers.conf", require => Anchor['jboss::installed'], notify => Service[$jboss::product], }
On systems with umask other than default 0022, this file may become unreadable by jboss::jboss_user, thus preventing jboss service from starting.
This command should be executed as $jboss::jboss_user
$jboss::jboss_user
The text was updated successfully, but these errors were encountered:
@Bejusek can you do this or some other team member should fix this ?
Sorry, something went wrong.
Sure, I'll fix it.
aa19dd8
Fixed by merging #57
Bejusek
No branches or pull requests
Right now the following code in internal/module/registerlayer.pp class creates
layers.conf
file as root.On systems with umask other than default 0022, this file may become unreadable by jboss::jboss_user, thus preventing jboss service from starting.
This command should be executed as
$jboss::jboss_user
The text was updated successfully, but these errors were encountered: