Date: Sat, 29 Sep 2001 17:37:11 -0500 From: Mike Meyer <mwm@mired.org> To: Chip <chip@wiegand.org> Cc: questions@freebsd.org Subject: Re: A general ports question/sylpheed port Message-ID: <15286.19735.111449.433967@guru.mired.org> In-Reply-To: <01092913284709.96094@chip.wiegand.org> References: <15286.8237.151174.565732@guru.mired.org> <01092913284709.96094@chip.wiegand.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chip <chip@wiegand.org> types: > On Saturday 29 September 2001 12:25, Mike Meyer wrote: > > Chip <chip@wiegand.org> types: > > Probably. That library is in x11-toolkits/gtk-engines. It's also > > possible that the port that installs that library was installed, then > > pkg_deleted without the port being cleaned. So do a "make install" for > > that port. If nothing happens, then you've got that later situation, > > so you can do "make reinstall" to install it. If the install installs > > it, notify the port maintainer of the problem. > Thanks Mike, that took care of that message, now I get another: You've got two different problems. > Gdk-WARNING **: shmget failed: error 28 (No space left on device) Gdk is trying to get some shared memory, and the kernel couldn't find enough to satisfy the request. You have to have the SysV shared memory primitives in the kernel. They are in the GENERIC kernel, so you should be able to add them if you're running a custom kernel that doesn't have them. If you are running GENERIC, then there may not be enough shared memory for what you're doing. "ipcs -mb" will show you the shared memory segments and sizes. "ipcs -M" will give you maximums allowed by the kernel. Increasing those require a custom kernel. See the ipcs man page and the LINT config file. One last thing - "ipcs -mo" will show you the number of processes using a shared memory segment. If that number is 0, you can delete the segment and try again. > bind: Permission denied Bind is a networking system call as well as a service - it attaches a socket to some specific address; either an IP port number or a Unix domain socket. If it's the former, it tried to bind to a port less than 1024; if the former it tried to bind to a file in a directory you can't write to. > I don't know which device that message is referring to, I check disk space > with df and I have gigabytes of free space on all partitions except procfs > which is at 100% (I don't know if that's okay or not). shmget is returning an "no space" error, which generates the message about "No space left on device". The space you're out of is shared memory; the reference to a device is confusing in this case. > I don't understand the bind message also, I am on a regular workstation, I > don't think bind is running on this one. That error message is also confusing - it looks like the message is from the program "bind", but the bind program is actually named "named". Which is why I'm assuming it's a bind system call that failed. The application should do a better job on this one. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15286.19735.111449.433967>