SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/05/01 14:08 2 Comments
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

groupwiseprotectedmemory

GroupWise Protected Memory

Protected Memory

Groupwise, being one of the best email systems in the world, could be a pain in the ass. Run solely on a fast and reliable server and you will do just fine, but most times, that's not the way it works. You don't always have a spare server available, so maybe there's also running iManager, or ZENworks on it. But email is more important, especially according to your manager. Downtime is not acceptable, so this is what you do, you run it in protected memory space. This makes sure you can always restart your groupwise services without a chance on freezing the server. What is does, it actually isolates the groupwise software and all needed libraries and modules from the rest of the system, making it think it runs on its own. If you want to unload the software and it hangs, you kill the memory space, reload the software and it runs again.

Changes

To configure groupwise to run in protected memory space you have to edit the autoexec.ncf file. Add the following lines to your file, overwriting the old groupwise load lines:

#
# GroupWise begin
# Load GroupWise in Protected Memory Space
# Done by Sjoerd
# 15 july 2008
# sjoerd [@] getshifting.com
# Tested on Netware 6.5
# 
protect grpwise.ncf
delay 10
protect gwia.ncf
delay 10
protect strtweb.ncf
delay 10
#
# GroupWise end
#

Result

You now have three separate address spaces:

  • grpwise.ncf
  • gwia.ncf
  • strtweb.ncf == Killing == There are two ways for killing these address spaces:
  • Commandline:
    • First unload the modules in the address space
      • unload address space=addr_space_name
    • If that doesn't work kill the entire address space
      • unload kill address space=addr_space_name
        • Note that if you want to script these commands you should put a delay of about 10 seconds in between.
  • Novell Remote Manager:
    nrmprotectedmemory.jpg
    == More memory space commands == === Run a module in a specific memory space ===
  • load address space=addr_space_name <module>
    • example: load address space=gwia.ncf libc.nlm === Unload a module from a specific memory space ===
  • unload address space=addr_space_name <module> === See a list of memory spaces ===
  • protection
    • This will give you a list of all address spaces and their loaded modules
  • Through monitor:
    • Go to virtual memory and select address spaces

References

Novell links: Running GW Agents in Protected Memory Space
Load files: grpwise.ncf

LOAD SYS:\SYSTEM\GWMTA @GWDOMAIN.MTA

LOAD SYS:\SYSTEM\GWPOA @GWPO.POA

gwia.ncf

load SYS:\SYSTEM\gwia @gwia.cfg

strtweb.ncf

load SYS:SYSTEM\gwinter @WEBAC70A.waa
You could leave a comment if you were logged in.
groupwiseprotectedmemory.txt · Last modified: 2013/04/30 14:31 by sjoerd