search for: working_dir

...entos 5 and I'm sure that I've missed something. After doing the initial installation, I get a 404 when I get to the part of the instructions that tell me to go to http://localhost/ledgersmb/admin.pl /etc/httpd/conf.d/ledgersmb.conf contains the following line: Alias /usr/share/ledgersmb WORKING_DIR /usr/share/ledgersmb exists and contains a file named admin.pl /etc/httpd/conf/httpd.conf contains the following line: Include conf.d/*.conf But when I go to http://localhost/ledgersmb/admin.pl I get this entry in the apache log: 127.0.0.1 - - [08/Aug/2009:15:47:30 -0600] "GET /ledgersmb/...

...s working, but i need a AD user for my batch to work. Is it a bug , a limitation or i miss something ? Thank for any help scheduled_task { ''test'': ensure => present, enabled => true, command => ''C:\test\test.bat'', working_dir => ''C:\test'', user => ''DOMAIN\oper'', password => ''xxxxx'', trigger => { schedule => daily, start_date => '...

...on}-%{release}-root-%(%{__id_u} -n) BuildRequires: perl #Requires: %description MinGW is a set of include files and import libraries that allow one to use GCC to build native Windows applications that use vendor-supplied runtime. %prep %setup -q -n %{cross_tool_ver} perl -pi -e "s(assume WORKING_DIR.+)(assume WORKING_DIR ${RPM_BUILD_DIR}/mingw-3.4.5)" x86-mingw32-build.sh.conf perl -pi -e "s(assume PACKAGE_DIR.+)(assume PACKAGE_DIR ${RPM_SOURCE_DIR})" x86-mingw32-build.sh.conf perl -pi -e "s(assume INSTALL_DIR.+)(assume INSTALL_DIR ${RPM_BUILD_ROOT}/opt/mingw)" x86...

I''m trying to use create_resources to create a series of files with semi-custom content based on a template. This is what I have: foo.conf.erb: Name "<%= name %>" WorkingDir "<%= working_dir %>" ... a bunch of static entries YAML: configs: config1: Name: app1 WorkingDir: /var/app1 config2: Name: app2 WorkingDir: /var/app2 ... config100: Name: app100 WorkingDir: /var/app100 manifest: class app { create_resources(app::virtualApps, hiera...

Hi: Reading Red Hat''s Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What''s the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as

...r/lib/glusterd/geo-replication/secret.pem change_detector: changelog use_meta_volume: true session_owner: a1c74931-568c-4f40-8573-dd344553e557 state_file: /var/lib/glusterd/geo-replication/mvol1_gl-node5-int_mvol1/monitor.status gluster_params: aux-gfid-mount acl remote_gsyncd: /nonexistent/gsyncd working_dir: /var/lib/misc/glusterfsd/mvol1/ssh%3A%2F%2Froot%40192.168.178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1 state_detail_file: /var/lib/glusterd/geo-replication/mvol1_gl-node5-int_mvol1/ssh%3A%2F%2Froot%40192.168.178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1-detail.status gluster_command_dir: /usr/sbin/ p...

...m > change_detector: changelog > use_meta_volume: true > session_owner: a1c74931-568c-4f40-8573-dd344553e557 > state_file: /var/lib/glusterd/geo-replication/mvol1_gl-node5-int_mvol1/ > monitor.status > gluster_params: aux-gfid-mount acl > remote_gsyncd: /nonexistent/gsyncd > working_dir: /var/lib/misc/glusterfsd/mvol1/ssh%3A%2F%2Froot%40192.168. > 178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1 > state_detail_file: /var/lib/glusterd/geo-replicat > ion/mvol1_gl-node5-int_mvol1/ssh%3A%2F%2Froot%40192.168. > 178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1-detail.status > gluster...

...ngelog > use_meta_volume: true > session_owner: a1c74931-568c-4f40-8573-dd344553e557 > state_file: > /var/lib/glusterd/geo-replication/mvol1_gl-node5-int_mvol1/monitor.status > gluster_params: aux-gfid-mount acl > remote_gsyncd: /nonexistent/gsyncd > working_dir: > /var/lib/misc/glusterfsd/mvol1/ssh%3A%2F%2Froot%40192.168.178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1 > state_detail_file: > /var/lib/glusterd/geo-replication/mvol1_gl-node5-int_mvol1/ssh%3A%2F%2Froot%40192.168.178.65%3Agluster%3A%2F%2F127.0.0.1%3Amvol1-detail.status >...

...ib/glusterd/geo-replication/secret.pem change_detector: changelog use_meta_volume: true session_owner: 2f5de6e4-66de-40a7-9f24-4762aad3ca96 state_file: /var/lib/glusterd/geo-replication/mvol1_gl-slave-01-int_svol1/monitor.status gluster_params: aux-gfid-mount acl remote_gsyncd: /nonexistent/gsyncd working_dir: /var/lib/misc/glusterfsd/mvol1/ssh%3A%2F%2Froot%4082.199.131.135%3Agluster%3A%2F%2F127.0.0.1%3Asvol1 state_detail_file: /var/lib/glusterd/geo-replication/mvol1_gl-slave-01-int_svol1/ssh%3A%2F%2Froot%4082.199.131.135%3Agluster%3A%2F%2F127.0.0.1%3Asvol1-detail.status gluster_command_dir: /usr/sbin...

...et.pem >change_detector: changelog >use_meta_volume: true >session_owner: 2f5de6e4-66de-40a7-9f24-4762aad3ca96 >state_file: >/var/lib/glusterd/geo-replication/mvol1_gl-slave-01-int_svol1/monitor.status >gluster_params: aux-gfid-mount acl >remote_gsyncd: /nonexistent/gsyncd >working_dir: >/var/lib/misc/glusterfsd/mvol1/ssh%3A%2F%2Froot%4082.199.131.135%3Agluster%3A%2F%2F127.0.0.1%3Asvol1 >state_detail_file: >/var/lib/glusterd/geo-replication/mvol1_gl-slave-01-int_svol1/ssh%3A%2F%2Froot%4082.199.131.135%3Agluster%3A%2F%2F127.0.0.1%3Asvol1-detail.status >gluster_comman...