Re: mlock(2) results in Resource temporarily unavailable on FreeBSD/amd64 9.0-STABLE
On Thu, 16 Feb 2012 09:47+0100, Trond Endrestøl wrote: > I have a system running FreeBSD/amd64 9.0-STABLE as of > Tue Jan 10 16:22:34 CET 2012. > > Every attempt by the root user to use the mlock(2) system call results > in Resource temporarily unavailable (EAGAIN, 35). > > I'm using bash and ulimit -l says there's no restriction on the amount > of locked memory: > > root@hostname:~>ulimit -l > unlimited > > Is this typical for the amd64 arch? Is this documented somewhere? > The mlock(2) system call works as expected on the i386 arch. The system is question is running ZFS at full steam, and the ARC might be to blame as nearly all physical memory is placed in the Wired category: Mem: 97M Active, 188M Inact, 7175M Wired, 193M Cache, 400K Buf, 249M Free This system has: real memory = 8589934592 (8192 MB) avail memory = 8234950656 (7853 MB) The solution might be to decrease vfs.zfs.arc_max from 7216345088 to a more sane number like 4096M. > GnuPG and other software would benefit from a useable mlock(2) on > the amd64 arch. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. dir. 61 14 54 39, | Office.: +47 61 14 54 39, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
mlock(2) results in Resource temporarily unavailable on FreeBSD/amd64 9.0-STABLE
I have a system running FreeBSD/amd64 9.0-STABLE as of Tue Jan 10 16:22:34 CET 2012. Every attempt by the root user to use the mlock(2) system call results in Resource temporarily unavailable (EAGAIN, 35). I'm using bash and ulimit -l says there's no restriction on the amount of locked memory: root@hostname:~>ulimit -l unlimited Is this typical for the amd64 arch? Is this documented somewhere? The mlock(2) system call works as expected on the i386 arch. GnuPG and other software would benefit from a useable mlock(2) on the amd64 arch. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. dir. 61 14 54 39, | Office.: +47 61 14 54 39, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0"
on 26/03/2011 11:10 O. Hartmann said the following: > Updating ports and source of my FreeBSD 9.0-CURRENT/amd64 host, equipted with > a > AMD/ATi HD4830 graphics board driven by X11 xf86-video-ati driver (which has > been recently update as far as I saw), > resulted this morning in an 'un-login-able' box. > > I see the xdm-login requester, but after successfully login, I see for a > second > the desktop (windowmaker), but X11 immediately dies and resets to the xdm > requester again. Are you subscribed to our x11 list? It's quite low volume. Please see recent messages in its archive, perhaps they could help you. -- Andriy Gapon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0"
Updating ports and source of my FreeBSD 9.0-CURRENT/amd64 host, equipted with a AMD/ATi HD4830 graphics board driven by X11 xf86-video-ati driver (which has been recently update as far as I saw), resulted this morning in an 'un-login-able' box. I see the xdm-login requester, but after successfully login, I see for a second the desktop (windowmaker), but X11 immediately dies and resets to the xdm requester again. Login from another box and examining the ~/.xsession-errors shows only this entry: --- foo.bar.org being added to access control list XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0" after 29 requests (29 known processed) with 0 events remaining. wmaker warning: got signal 15 - exiting... --- Recompiling xdm and xorg-server ( I did this desperately in the first place) didn't help very much. I do not dare to update all the other boxes in my lab, since I suspect a similar problem since they have all the same or similar hardware (AMD graphics hardware, running X11, running FreeBSD 9.0-CURRENT/amd64). What to do? What changed? Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
read -1 errno 35 Resource temporarily unavailable
Greetings, I have encountered a problem on my FreeBSD that I cannot seem to resolve. The problem started with my install of postfix/sendmail reporting "postfix/sendmail[56108]: fatal: (1001): error writing queue file: Broken pipe". Through ktrace, I was able to identify the an EAGAIN error: read -1 errno 35 Resource temporarily unavailable. The folks on the postfix suggested that I should do a kernel upgrade, which I was able to complete (5.2 -> 5.4). However, the EAGAIN problem with postfix/sendmail still hasn't gone away. Further more, mutt is now having troubles. When opening mutt, it hangs on opening the user's mailbox under /var/mail/. ktrace shows: read -1 errno 35 Resource temporarily unavailable. I'm not sure what I should do next. Can you provide me with advise / pointers on how to go about to do further troubleshooting or how to resolve it? Thanks in advance, Catherine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resource temporarily unavailable crash in vi
I've experienced this bug on several occasions. Each time I was using vi over a ssh session. X11 was not loaded on the system. I never did figure it out, and after a reinstall the problem did not occur often. I suspect it has something to do with virtual memory. On Jun 12, 2004, at 1:17 PM, Benjamin Lutz wrote: Hello, I'm lately experiencing the "Resource temporarily unavailable" crash in vi a lot. I've had the same thing happen in other programs (eg, cvs, while it was waiting for input), so it's not something that's specific to vi. Someone even had it happen with cat: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/ 0497.html I went about investigating this occurance. I added an abort() to strerror() so I would get a coredump before the error message is printed. The results are a bit surprising: #0 0x2814406f in kill () from /lib/libc.so.5 #1 0x28138da8 in raise () from /lib/libc.so.5 #2 0x281ae493 in abort () from /lib/libc.so.5 #3 0x28193be3 in strerror () from /lib/libc.so.5 #4 0x08053e15 in free () #5 0x0804bcc0 in free () #6 0x0804b929 in free () #7 0x08050b85 in free () #8 0x0807e331 in free () #9 0x0807d12e in free () #10 0x0807cb8c in free () #11 0x08053307 in free () #12 0x0804b063 in free () #13 0x0804a3b9 in free () I then found these two postings that seem to point in the correct direction: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/ 0094.html http://monkey.org/openbsd/archive/misc/0310/msg01101.html This vi thing has happened most often while i working in KDE's Konsole. I'd open a new window, switch back to the old one, and vi would have crashed. It also happens when I'm starting vi in a Konsole. Now, I think the problem (or one of the programs that make it apparent) is Konsole. However, before filing a bug report, I'd like to get some more information. If you've ever encountered this bug, what were the circumstances? If you've researched it some, what did you find out? Greetings Benjamin Lutz Lucas Holt [EMAIL PROTECTED] FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) 'Mmm... forbidden donut' -- Homer Jay Simpson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Resource temporarily unavailable crash in vi
Hello, I'm lately experiencing the "Resource temporarily unavailable" crash in vi a lot. I've had the same thing happen in other programs (eg, cvs, while it was waiting for input), so it's not something that's specific to vi. Someone even had it happen with cat: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/0497.html I went about investigating this occurance. I added an abort() to strerror() so I would get a coredump before the error message is printed. The results are a bit surprising: #0 0x2814406f in kill () from /lib/libc.so.5 #1 0x28138da8 in raise () from /lib/libc.so.5 #2 0x281ae493 in abort () from /lib/libc.so.5 #3 0x28193be3 in strerror () from /lib/libc.so.5 #4 0x08053e15 in free () #5 0x0804bcc0 in free () #6 0x0804b929 in free () #7 0x08050b85 in free () #8 0x0807e331 in free () #9 0x0807d12e in free () #10 0x0807cb8c in free () #11 0x08053307 in free () #12 0x0804b063 in free () #13 0x0804a3b9 in free () I then found these two postings that seem to point in the correct direction: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/0094.html http://monkey.org/openbsd/archive/misc/0310/msg01101.html This vi thing has happened most often while i working in KDE's Konsole. I'd open a new window, switch back to the old one, and vi would have crashed. It also happens when I'm starting vi in a Konsole. Now, I think the problem (or one of the programs that make it apparent) is Konsole. However, before filing a bug report, I'd like to get some more information. If you've ever encountered this bug, what were the circumstances? If you've researched it some, what did you find out? Greetings Benjamin Lutz pgpC6E6COJItW.pgp Description: PGP signature
vi, threading, EAGAIN, nonblocking (was: Error: input: Resource temporarily unavailable)
[Sorry if this has been answered; I'm catching up on freebsd-questions
and I haven't seen it in the next seven or eight digests.]
Tim Gustafson writes:
>I am getting the following error in "vi" pretty consistently:
>Error: input: Resource temporarily unavailable
>Usually I get this at every attempt I make to run vi.
Here's the scenario I found for this:
A threaded program (before 5.x and the new threading system) will turn
on Nonblocking on ALL the program's file descriptors, including stdin,
stdout, and stderr. This setting is not on the process but on the open,
which is shared between processes (and thus, between various programs
that run at a given terminal, including the shell). An unsophisticated,
innocent program will try to do a read(2) on the terminal, expecting to
block waiting for input. Instead, it will receive an EAGAIN, which
basically means ``use poll(), select(), or kevent() to wait until the
input is _really_ there.'' So now vi/nvi has an input terminal that
doesn't behave like a terminal is supposed to behave; it's getting an
EAGAIN, and it does the safest thing it knows: it reports the problem
and goes away.
I use this little program to check for Nonblocking and restore the
normal (Blocking) state on the tty:
#include
#include
#include
#include
bool checkfd( int fd );
int
main()
{
return checkfd( 0 )
&& checkfd( 1 )
&& checkfd( 2 ) ? 0 : 1;
}
bool
checkfd( int fd )
{
int flags = fcntl( fd, F_GETFL, 0 );
if( flags == -1 )
{
cerr << "Fd " << fd << ": " << strerror( errno ) << endl ;
return false;
}
cout << fd << ( ( flags & O_NONBLOCK ) ? " nonblocking" : " blocking" )
<< endl ;
if( ! ( flags & O_NONBLOCK ) )
cerr << "blocking" << endl ;
else
{
cerr << "nonblocking" << endl ;
if( fcntl( fd, F_SETFL, flags & ~O_NONBLOCK ) == -1 )
{
cerr << "Couldn't set O_NONBLOCK: " << errno
<< " " << strerror( errno ) << endl ;
return false;
}
}
return true;
}
Hope this helps.
Mark Terribile
__
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Error: input: Resource temporarily unavailable
On Thu, 27 May 2004, Gustafson, Tim wrote: > I am getting the following error in "vi" pretty consistently: > > Error: input: Resource temporarily unavailable > > Usually I get this at every attempt I make to run vi. Every now and > then I'll somehow manage to stay in vi however long I want. It seems > that if it's going to bomb, it bombs in the first 30 seconds of running > the program. Otherwise, it doesn't happen at all. > > No other programs do this, as far as I know. > > I have tried installing the nvi-devel port to see if maybe this is fixed > in a new version, but it does the exact same thing. I even rebuilt the > kernel and world after a cvsup to make sure something wasn't broken, but > that didn't work wither. I have tried switching shells from bash to > just sh to see if it's related somehow to bash, but that did not have > any effect either. > > I am currently running FreeBSD 4.9-RELEASE-p8 i386 > > This problem pops up about once a month and then seems to go away by > itself after a few days, but I would really like to know what is causing > it. I have searched the FreeBSD mailing list archives and found a few > references to changing some flag in my shell, and I followed their > instructions, but it did not help. > > Obviously, it is a real pain in the neck since I use vi exclusively and > I despise having to us pico for anything. > > If anyone has any idea how I can fix this, I would really appreciate it. Are you using this when SSH'd into a remote system? I started seeing this after the SSH changed to introduce "untrusted X11 forwarding", but it lasted for about a day and then vanished. FYI, the problem is likely that a system call is returning EAGAIN, and that's getting pushed up through the vi ncurses or another component which doesn't know how to handle that error code, so simply exits. There used to be a similar problem with EINTR as a result if the window change signal and certain bits of vi's state machine. If you can reproduce this easily, could you try running vi under ktrace, then see if you can trigger the problem? The last few dozen lines of kdump would be very helpful, as it would identify the system call that's returning EAGAIN. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Error: input: Resource temporarily unavailable
I am getting the following error in "vi" pretty consistently: Error: input: Resource temporarily unavailable Usually I get this at every attempt I make to run vi. Every now and then I'll somehow manage to stay in vi however long I want. It seems that if it's going to bomb, it bombs in the first 30 seconds of running the program. Otherwise, it doesn't happen at all. No other programs do this, as far as I know. I have tried installing the nvi-devel port to see if maybe this is fixed in a new version, but it does the exact same thing. I even rebuilt the kernel and world after a cvsup to make sure something wasn't broken, but that didn't work wither. I have tried switching shells from bash to just sh to see if it's related somehow to bash, but that did not have any effect either. I am currently running FreeBSD 4.9-RELEASE-p8 i386 This problem pops up about once a month and then seems to go away by itself after a few days, but I would really like to know what is causing it. I have searched the FreeBSD mailing list archives and found a few references to changing some flag in my shell, and I followed their instructions, but it did not help. Obviously, it is a real pain in the neck since I use vi exclusively and I despise having to us pico for anything. If anyone has any idea how I can fix this, I would really appreciate it. Tim Tim Gustafson MEI Technology Consulting, Inc [EMAIL PROTECTED] (516) 379-0001 Office (516) 480-1870 Mobile/Emergencies http://www.meitech.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Resource temporarily unavailable"
On a 4-STABLE box I am sometimes editing a file in preparation for an email, and the session "dies" with a "Resource temporarily unavailable" message. This is getting really old - there are no other messages anywhere, and vmstat (for example) shows nothing interesting. How can I figure out what is going wrong (so I can find and fix the root cause)? H ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
On Tue, Jul 15, 2003 at 12:43:40AM +0200, Matthias Buelow wrote: > Mikhail Teterin writes: > > >Every once in a while, a vi-session dies on me with: > > > > input: Resource temporarily unavailable > > Are you running ksh93 per chance? I've seen this after I started an > OpenGL program such as xscreensaver-demo from ksh93 (however that > could have influenced the terminal settings or whatever is beyond my > current understanding.) I've seen this intermittently on both -CURRENT and with 4.7; whatever causes it seems to corrupt the state of the tty, as the only thing that seems to reset is entering/exiting gdb. I use ksh93. Andrew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
=>Every once in a while, a vi-session dies on me with: => => input: Resource temporarily unavailable =Are you running ksh93 per chance? I've seen this after I started an =OpenGL program such as xscreensaver-demo from ksh93 (however that =could have influenced the terminal settings or whatever is beyond my =current understanding.) I don't use ksh, but it does, indeed, happen when the machine is under heavy use (compiles and what-not -- xscreensaver-demo would, probably, qualify too). -mi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
- Original Message - From: "Matthias Buelow" <[EMAIL PROTECTED]> To: "Mikhail Teterin" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, July 14, 2003 3:43 PM Subject: Re: ``Resource temporarily unavailable'' in vi > Mikhail Teterin writes: > > >Every once in a while, a vi-session dies on me with: > > > > input: Resource temporarily unavailable > > Are you running ksh93 per chance? I've seen this after I started an > OpenGL program such as xscreensaver-demo from ksh93 (however that > could have influenced the terminal settings or whatever is beyond my > current understanding.) I am running ksh93 and have seen this, too, although not often and not recently (in the past month) on 4-stable. Joshua ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
Mikhail Teterin writes: >Every once in a while, a vi-session dies on me with: > > input: Resource temporarily unavailable Are you running ksh93 per chance? I've seen this after I started an OpenGL program such as xscreensaver-demo from ksh93 (however that could have influenced the terminal settings or whatever is beyond my current understanding.) -- Matthias Buelow; [EMAIL PROTECTED],informatik.uni-wuerzburg.de} ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
On Mon, Jul 14, 2003 at 06:08:32PM -0400, Mikhail Teterin wrote: > Every once in a while, a vi-session dies on me with: > > input: Resource temporarily unavailable > > What does it mean, why does it happen, and how can I prevent it? I suspect vi's not handling an EAGAIN error return. I get this on -stable when ripping a cd with grip/cdda2wav. Are you doing something that runs at very high priority when it happens? Judging from the comments in /usr/src/sys/errno.h, it could also be that there is a resource deadlock and vi is not translating the errno correctly. Anyway, pending a fix in vi to handle retryable errors, the workaround is not to do whatever it is that you're doing at the same time. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
``Resource temporarily unavailable'' in vi
Every once in a while, a vi-session dies on me with: input: Resource temporarily unavailable What does it mean, why does it happen, and how can I prevent it? Thanks a lot! -mi P.S. Running recent -current. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
linux_socketcall() returns Resource temporarily unavailable
Hello, I have just installed FreeBSD 4.8-RELEASE and decided to try to run a Quake3 server using Linux emulation. I've found that the q3ded program consumes 99% of the CPU, leading me to believe there may be a problem with the program or with the Linux emulation feature in FreeBSD. Some details about my installation: > uname -a FreeBSD cutest.daemons.net 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Mon Mar 31 02:11:00 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > pkg_info | grep linux linux_base-7.1_2The base set of packages needed in Linux mode The top output: CPU states: 16.7% user, 0.0% nice, 83.3% system, 0.0% interrupt, 0.0% idle Mem: 34M Active, 1712M Inact, 155M Wired, 103M Cache, 199M Buf, 5148K Free Swap: 4080M Total, 4080M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 93552 clay 58 0 80156K 4260K RUN 20:50 97.07% 97.07% q3ded 93568 clay 29 0 1880K 1176K RUN 0:00 5.78% 1.71% top truss output: gettimeofday(0xbfbfb9d8,0x0) = 0 (0x0) linux_time(0xbfbfee84)= 1049588547 (0x3e8f7343) gettimeofday(0xbfbfee7c,0x0) = 0 (0x0) linux_socketcall(0xc,0xbfbfb970) ERR#35 'Resource temporarily unavailable' The q3ded program appears to be in a loop, as it keeps executing these same system calls. I believe the linux_socketcall() corresponds to recvfrom() since q3ded creates a UDP socket and waits for incoming messages on that port. I searched Google and the FreeBSD mailing list archive but could only find one thread about this problem, but it was from December 2000 and did not mention a fix. Does anyone know what is causing this problem and how to fix it? Thanks, Clay McClure Please CC: me as I am not subscribed to the list. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resource temporarily unavailable
On Tue, Mar 18, 2003 at 09:03:32AM +0100, Jan Blomqvist wrote: > Hi! > I have 800mhz 500mb node with freebsd 4.1, I often get this "Resource > temporarily unavailable" > I have problem to find out what kind of Resource its problem with, when I do > top command everything looks ok lots of memory free and like 80% idle, and > we have done some changes in the kernel "options MAXMEM=(512*1024) > options SHMMNI=64"and also increased maxusers to 128.This is a > example of error message: Hi, Just a couple of wild guesses : - I suppose you have no particular maxprocess limit or whatever for your login class in /etc/login.conf? You can always have a look at login.conf(5) - What does 'ps auxww' look like when this happens? Anything surprising there? 'top' only shows the first so much heavier processes, so you might not see everything. - On my box here I just ran a little test and with all limits set to 'unlimited' in login.conf I can trigger this error with a recursive shell script calling itself. It happens when about 475 processes have been spawned, and then they all die eventually and everything returns to normal. Hope this helps a bit, but people on the list have probably more information and also more relevant about this matter... good luck :-) Olivier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Resource temporarily unavailable
Hi! I have 800mhz 500mb node with freebsd 4.1, I often get this "Resource temporarily unavailable" I have problem to find out what kind of Resource its problem with, when I do top command everything looks ok lots of memory free and like 80% idle, and we have done some changes in the kernel "options MAXMEM=(512*1024) options SHMMNI=64"and also increased maxusers to 128.This is a example of error message: Formatting page, please wait...Cannot fork: Resource temporarily unavailable /usr/bin/groff:fatal error: fork: Resource temporarily unavailable Failed. pclose: No such file or directory Cannot fork: Resource temporarily unavailable Error executing formatting or display command. system command exited with status 512 Thanks for your interest /Jan Blomqvist To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
resource temporarily unavailable
Hello, I am running release 4.6.2 and recently I've been getting the following error: Error: input: Resource temporarily unavailable This occurs intermittently while I'm editing files in vi. Can anyone tell me what's going on? Thanks. -- Daniel Fisher msg07843/pgp0.pgp Description: PGP signature
