Start GroupWise agent consoles on start-up running SLES

  • 7014924
  • 16-Apr-2014
  • 18-Apr-2014


Novell GroupWise


Start GroupWise agent consoles on start-up running Linux
Start GroupWise agents in show mode on start-up


The solution below will make it so the agents do not start up until logging into the X session.  Everyones system is set up differently so the script will need to edited to fit the needs of the server being changed.
  1. Create a new file and name it something like
  2. Open the file that was just created and edit it so it has something similar to the script below

    /opt/novell/groupwise/agents/bin/gwmta --show @ /opt/novell/groupwise/agents/share/gwdom.mta &
    /opt/novell/groupwise/agents/bin/gwpoa --show @ /opt/novell/groupwise/agents/share/gwpo.poa &
    /opt/novell/groupwise/agents/bin/gwia --show @ /opt/novell/groupwise/agents/share/gwia.cfg &
    rcgrpwise start gwdva

    /opt/novell/groupwise/agents/bin/* is the path to the agent executable
    @ /opt/novell/groupwise/agents/share/* is the path to the agent configuration file
    rcgrpwise start gwdva is for the agents such as the DVA that do not have gui consoles
    Make sure to include the "&" at the end of the start-up command or the next commands will not run
  3. Adjust the script to fit the systems paths and number of agents running on the server
  4. Save and exit the file
  5. Make the file executable, E.G. if a terminal is being used, type chmod + x
  6. Verify that the script that has been created will work properly by typing rcgrpwise stop and then type ./ in the same directory that it was created
  7. If everything works as expected, then the GroupWise agents can be stopped from coming up on startup.  In a terminal session, type chkconfig grpwise off
  8. At this point, the script needs to be added to startup.  Type gnome-session-properties
  9. Click Add and in name field, type the desired name for startup script, for command type the path to the created script E.G /root/desktop/ and Comment can be whatever is desired.  Click Add to save
  10. Reboot the server and log in to the X session to verify that the start-up script works properly