Subject: Re: Re : [netatalk-admins] "no more room on device"
From: Les Barstow (lbarstow@entire.com)
Date: Wed Mar 10 1999 - 14:09:08 EST
Well, the solution was...
Reset the atalkd.conf file to 'hme0' with no other arguments (Solaris
needs an interface to start). Apparently netatalk was set to an invalid
net, or the net number chosen previously was taken.
I've chmod'ed the atalkd.conf a-w so it always gets a number
dynamically.
Les Barstow
Yann Bizeul wrote:
>
> Yes, but netatalk is not Solaris... Macintosh use frequently this term,
> perhaps netatalk too... mmm... nothing in /var/log/messages about that ?
>
> On Tue, 9 Mar 1999, Les Barstow wrote:
>
> >
> >
> > Yann Bizeul wrote:
> > >
> > > ey, did u check the space left on your disks ?
> >
> > Yah. Lots of space on all devices, including swap/tmp. Solaris never
> > uses the term "room" when complaining about things like that. It either
> > says "no space left on device" or "filesystem full", depending on the
> > access mode.
> >
> > Les
> >
> > > This message sounds like there is not enough space on a disk...
> > >
> > > > We are receiving an error message, "no more room on device", from our
> > > > netatalk 1.4b2 (with bfree, macos8, and solarisegain patches) on an
> > > > Ultra 5 running Solaris 2.5.1 (netatalk was compiled with gcc 2.7.2.3).
> > > > This happens during the atalkd startup. The atalkd.conf file seems to
> > > > contain valid information, but none of the services start.
> > > >
> > > > Any clues on this error?
> >
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:25 EST