It is currently Fri, 27 Apr 2018 00:02:51 GMT

Author Message
 forceload: sys/semsys forceload: sys/shmsys
Actually, I meant
I have a third party middleware package which is loaded at boot time.
It uses shared memory and semaphores. When the server is rebooted, the
the middleware performance is terrible. If the daemons are then manually,
restarted, everything works fine. So I suspect that when at boot time ,
the middleware starts, there are some race conditions related to the fact that
shared memory and semaphore support are loaded at first reference. Can this
make sense? Would forceloading IPC with  forceload: sys/semsys
forceload: sys/shmsys help?

Any help will be greatly appreciated.


 Fri, 02 Jan 2004 21:16:35 GMT   
 forceload: sys/semsys forceload: sys/shmsys
How about changing the application startup script to sleep 60, and then
startup the app itself?

 Sat, 03 Jan 2004 04:04:15 GMT   
 forceload: sys/semsys forceload: sys/shmsys
That's what I thought, too. But this does not help. Btw, the daemons
don't detach from stdout. That should not be causing our problems, right?
On the other hand, if a daemon process is loaded at boot time, where its
stdout would be going?

 Sat, 03 Jan 2004 09:33:49 GMT   
   [ 3 post ] 

Similar Threads

1. forceload: sys/msgsys

2. comp.sys.hp comp.sys.sgi comp.sys.sun comp.unix.ultrix comp.unix.wizards

3. comp.sys.mac.misc comp.sys.mac.system comp.sys.mac.apps

4. shmsys and semsys (default values?)

5. Q: Where does forceload (in /etc/system) look?

6. Where does forceload look?

7. forceload of drv/ide with SDS

8. forceload of misc/md_trans

9. forceload devices are permanently in memory?

10. forceload /drv/sd failed

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software