I'm using bric_queued for pub/dist with *bric_queued --username publisher
--password password*. Where publisher is a bric user I setup just for
handling scripted publishing tasks. Looking at the /etc/init.d/bricolage
startup script, I see it will also launch bric_queued at startup. However,
when I set the values:
DIST_USERNAME="publisher"
DIST_PASSWORD="password"
in that script and run:
% sudo /etc/init.d/bricolage start
I get this output:
Cannot open PID file /var/run/bric_queued.pid at /usr/local/bin/bric_queued
line 389.
[/usr/local/bin/bric_queued:424]
[/usr/local/bin/bric_queued:439]
[/usr/local/bin/bric_queued:226]
[/usr/local/bin/bric_queued:208]
bric_queued: started
Since, I'm running the startup script as root, I'm not sure what the problem
is. Perhaps the user *www-data*, is trying to launch bric_queued rather than
root, but does not have permission to write to /var/run? I'm just not sure.
Help!
ryan
--password password*. Where publisher is a bric user I setup just for
handling scripted publishing tasks. Looking at the /etc/init.d/bricolage
startup script, I see it will also launch bric_queued at startup. However,
when I set the values:
DIST_USERNAME="publisher"
DIST_PASSWORD="password"
in that script and run:
% sudo /etc/init.d/bricolage start
I get this output:
Cannot open PID file /var/run/bric_queued.pid at /usr/local/bin/bric_queued
line 389.
[/usr/local/bin/bric_queued:424]
[/usr/local/bin/bric_queued:439]
[/usr/local/bin/bric_queued:226]
[/usr/local/bin/bric_queued:208]
bric_queued: started
Since, I'm running the startup script as root, I'm not sure what the problem
is. Perhaps the user *www-data*, is trying to launch bric_queued rather than
root, but does not have permission to write to /var/run? I'm just not sure.
Help!
ryan