| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| We have all the patches on SunOS 5.9 and Provider-1 installs fine. If it starts on boot everything is hunky-dory. However, if we need to stop and start the mds with mdsstart/mdsstop, the processes attach to the terminal pts/N or console. The end result is that when the user logs out of the machine, the process gets killed. Normally, services should start with a '?' in the place of the terminal. In this case, it doesn't. We checked the scripts and environment variables - everything looks ok. Are we doing something wrong or how can we fix this? |
| |||
| Jim: Thanks for the very useful work-around. In the meantime, I also found the "answer." CheckPoint is very csh based. So I did was the following: edit .profile to check for the file /usr/bin/csh; then set shell to csh and changed the line: . /opt/CPshrd-R61/tmp/.CPprofile.sh to . /opt/CPshrd-R61/tmp/.CPprofile.csh once this .profile was sourced, it worked fine. I'm able to start the mds and logout without problem. |
| |||
| UPDATE Instead of changing the shell to csh, you can just create the file .cshrc in which include at the very least: # Running Check Point environment script source /opt/CPshrd-R61/tmp/.CPprofile.csh If I figure out why the sh script doesn't work, I'll post it here. |
| |||
| Problem found! When you use the bash so much, you forget what you didn't have with the Bourne shell. Anyway, the problem is that you can't run mdsstart from the Bourne shell and logout, because it doesn't have the ability to disown the process. This at first didn't make sense, but if you source the same CheckPoint script listed above with .sh on the end, and run it from a bash shell everything is fine. |
![]() |
| Thread Tools | |
| Display Modes | |
| |