I've just had a bit more of a fiddle, and even with the xinetd conf mods
specified in the Amanda installation docs for machines running the
client-side, 'amcheck' on the tape server hose wasn't getting access to the
disk devices via amandad on the Cobalt server...
The disk devices (/dev/hda1, etc.
2008/6/13 Jean-Louis Martineau <[EMAIL PROTECTED]>:
> Craig Dewick wrote:
>
>> ERROR: ziri: [could not access /dev/hda6 (/dev/hda6): Permission denied]
>> ERROR: ziri: [could not access /dev/hda2 (/dev/hda2): Permission denied]
>> ERROR: ziri: [could not access /dev/hda1 (/dev/hda1): Permission de
Craig Dewick wrote:
ERROR: ziri: [could not access /dev/hda6 (/dev/hda6): Permission denied]
ERROR: ziri: [could not access /dev/hda2 (/dev/hda2): Permission denied]
ERROR: ziri: [could not access /dev/hda1 (/dev/hda1): Permission denied]
which is rather strange as I've already made sure, as far
Hi,
I'm getting closer to having Amanda 2.5.2p1 working on my Cobalt Raq-4i
system which now runs StrongBolt OS (based on CentOS 4.4). The amandad
client running on the Cobalt system was complaining about /etc/amandates not
existing even though I don't think it gets used. On this Sunblade 1000
sys