Re: maxusers and random system freezes
With these settings, and that much physical RAM, you should set your KVA space to 3G (the default is 2G); have you? Most likely, you are running out of KVA space for mappings. Every now and this I hear people saying (mostly you :)) that some problems are KVA related or that the KVA must be increased. This makes me a bit curious, since I've never seen problems like that on Linux. It sounds for me, the not kernel hacker, a bit like something which should be set at boot time (or via sysctl). Have you got some pointers which explain FreeBSD's KVA ? Regards, Marc Premature optimization is the root of all evil. -- Donald E. Knuth To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: How to keep java code running after logout
I have installed FreeBSD 4.5 on my machine. I am also having 2 other machines running on linux. We have developed a code in java which we need to run in background for 24 hrs. In linux we use... java Code1 command to run our code in background. After starting this command we just logout from that terminal window. We have seen that on linux machine our code works fine in background. IIRC this depends on the shell. But IMHO it is normal behaviour that the child (your program) gets killed if the parent (the shell) got killed. You should read nohup(1). nohup is your friend. :-) But for 24x7 you could also use init(8). Under SysV you could write your program in /etc/inittab and under *BSD in /etc/ttys. So the program gets automatically started by init _and_ restarted if it crashes. msg36006/pgp0.pgp Description: PGP signature
