Another thing you can try is to make /usr group writable to the
"admin" group. And add your user on the admin group. Then installing
packages without sudo. The initial chowning of directories will
require sudo however.
On Wed, Dec 8, 2010 at 7:26 AM, Noah
Kantrowitz< >
wrote:
On Dec 7, 2010, at 3:08 PM, Christian Requena wrote:
Hi,This is specific to the service resource, but you could certainly build your
you can define your commands freely.
Example for tomcat.
Define what do you want to do (i.e. in an attribute file):
# start the serviceOverwrite the start,stop,... commands in your recipe:
default[:tomcat][:start]= (platform == 'windows') ?
'C:\Applications\tomcat\bin\catalina.sh start' : \
"sudo service tomcat
start"
# stop the service
default[:tomcat][:stop]= (platform == 'windows') ?
'C:\Applications\tomcat\bin\catalina.sh stop' : \
"sudo service tomcat
stop"
#
# get service status. TODO: windows!?
default[:tomcat][:status]="sudo service tomcat status"
...
service "tomcat" do
action :nothing
supports :start => true, :stop => true, :restart => true, :status =>
false
start_command node[:tomcat][:start]
stop_command node[:tomcat][:stop]
status_command node[:tomcat][:status]
restart_command "#{node[:tomcat][:stop]}&& #{node[:tomcat][:start]}"
end
...
own provider (which would be 99% identical to the existing RPM provider)
which uses sudo in the command.
--Noah
Archive powered by MHonArc 2.6.16.