Problems with Sun Client 5.8- could not access /dev/rdsk/c0t0d0s0: Permission denied

2004-02-18 Thread todd zenker
I've compiled amanda on SunOS 8 box ERROR! could not access /dev/rdsk/c0t0d0s0: Permission denied Give some ideas where to look I checked the following on client side - .amandahosts - /etc/services - /etc/inetd.conf Not sure what else to look for. Any ideas Thanks Todd E. Zenker CNE-GSFC NASA

Re: Problems with Sun Client 5.8- could not access /dev/rdsk/c0t0d0s0: Permission denied

2004-02-18 Thread Bram Metsch
On Wed, 18 Feb 2004 06:53:34 -0500 todd zenker [EMAIL PROTECTED] wrote: I've compiled amanda on SunOS 8 box ERROR! could not access /dev/rdsk/c0t0d0s0: Permission denied Give some ideas where to look I checked the following on client side - .amandahosts - /etc/services -

Re: Problems with Sun Client 5.8- could not access /dev/rdsk/c0t0d0s0: Permission denied

2004-02-18 Thread Christoph Scheeder
Hi, verry basic question, you have checked the permisions on /dev/rdsk/c0t0d0s0 on the client to make sure your amanda user has at least group-access to this device, do you? Christoph todd zenker schrieb: I've compiled amanda on SunOS 8 box ERROR! could not access /dev/rdsk/c0t0d0s0: Permission

Re: Problems with Sun Client 5.8- could not access /dev/rdsk/c0t0d0s0: Permission denied

2004-02-18 Thread Brian Cuttler
Todd, On my system (any version of solaris) /dev/rdsk/* devices are links to /devices/pcisomething/somethingelse/[EMAIL PROTECTED],0:h,raw for some n 0 and h which is some alpha = a. Check the 'real' devices in the /dev/ tree. At our site we have user=amanda group=sys for our amanda user and

Re: Problems with Sun Client 5.8- could not access /dev/rdsk/c0t0d0s0: Permission denied

2004-02-18 Thread Jon LaBadie
On Wed, Feb 18, 2004 at 01:05:44PM +0100, Bram Metsch wrote: On Wed, 18 Feb 2004 06:53:34 -0500 todd zenker [EMAIL PROTECTED] wrote: I've compiled amanda on SunOS 8 box ERROR! could not access /dev/rdsk/c0t0d0s0: Permission denied Give some ideas where to look I checked the

nfs mounted executable

2004-02-18 Thread DK Smith
Hello all, I was experimenting with a different installation strategy... That is, in order to not install amanda on every host... I am attempting to place a single amanda installation on a file server; making it available via an NFS share. The nfs-clients of the same architecture (in this

Re: nfs mounted executable

2004-02-18 Thread Paul Bijnens
DK Smith wrote: I was experimenting with a different installation strategy... That is, in order to not install amanda on every host... I am attempting to place a single amanda installation on a file server; making it available via an NFS share. The nfs-clients of the same architecture (in this

Re: nfs mounted executable

2004-02-18 Thread Jon LaBadie
On Wed, Feb 18, 2004 at 02:30:05PM -0800, DK Smith wrote: Hello all, I was experimenting with a different installation strategy... That is, in order to not install amanda on every host... I am attempting to place a single amanda installation on a file server; making it available via an

Re: nfs mounted executable

2004-02-18 Thread DK Smith
sometimes I do not see the forest for the trees... I looked briefly at the line above that one... ugh --enable-shared=PKGSbuild shared libraries default=yes thanks! I hope you are well! Don't know for sure, but --enable-static sounds like a winner.

Re: nfs mounted executable

2004-02-18 Thread DK Smith
Has anyone successfully used --enable-static ? I have not been able to determine the appropriate syntax. I have tried these three ways: --enable-static --enable-static=yes --enable-static=list of individual package names such as amcheck Cheers, DK