Amd is poorly designed the way it blocks and is overly sensative to one's
network setup. Your's is the first trouble I've heard of with back
grounding its invocation, and several were happy with it. I don't know
what to say. remove rev 1.127 if you like.
what's needed is a simple way
hi,
I have a problem with /etc/rc.d/amd, because of the line
command_args=
${amd_program} gets run in the background, ldconfig failes to cache libraries
in /usr/local/lib (which is automounted :-)
Is there realy a need for the ? amd will background itself after it's done
with the
On Sat, 07 Jun 2003 13:13:15 +0300
Danny Braniss [EMAIL PROTECTED] wrote:
hi,
I have a problem with /etc/rc.d/amd, because of the line
command_args=
${amd_program} gets run in the background, ldconfig failes to cache libraries
in /usr/local/lib (which is automounted :-)
Is
This may have been because of a missed merge from rcOG. How does the following
work for you?
Cheers.
it will fix my problem, but in an 'obscure way', just have to remember to
set amd_flags
my point is that amd should not be backgrounded by default, it does so anyway
once it managed to
On Sat, 07 Jun 2003 15:48:47 +0300
Danny Braniss [EMAIL PROTECTED] wrote:
context
I have a problem with /etc/rc.d/amd, because of the line
command_args=
[amd] gets run in the background, ldconfig failes to cache libraries
in /usr/local/lib (which is automounted :-)
/context
my
On Sat, Jun 07, 2003 at 09:04:46AM -0400, Mike Makonnen wrote:
On Sat, 07 Jun 2003 15:48:47 +0300
Danny Braniss [EMAIL PROTECTED] wrote:
context
I have a problem with /etc/rc.d/amd, because of the line
command_args=
[amd] gets run in the background, ldconfig failes to cache
