Ah, good point except in the case where you might have a Management station that manages multiple policies. If you open another policy (effectively "closing" the other policy ) to make changes you haven't removed the manage.lock file. I'm trying to figure out what the "command line" command is that actually "closes" the policy. It will be (relatively speaking) easy to build the script around it then. I'll let you know when I've got this working. Kevin > -----Original Message----- > From: DEAN Ivan [mailto:[EMAIL PROTECTED]] > Sent: Sunday, August 08, 1999 6:40 PM > To: 'Martin, Kevin' > Subject: RE: [FW1] policy source control FW1 > > > The removal of the manage.lock file? I would be very > interested in your > code for this, as change control has always been a weak point > with the GUI. > > Ivan Dean > > -----Original Message----- > From: Martin, Kevin [mailto:[EMAIL PROTECTED]] > Sent: Friday, 6 August 1999 2:53 > To: 'FW Digest'; 'fw-1-mailinglist' > Subject: [FW1] policy source control FW1 > > > > Ok, I've figured out ( kind of ) what takes place when the > GUI opens up a > policy and I've got a script made that will SCCS get the > policy, the objects > file, the rulebases.fws. Now, when I close the gui, how do I > check it back > in? What's my trigger? Any ideas? > > Thanks. > > Kevin Martin > Bank of America - CRT > Firewall/DNS/SMTP/Network Admin. > [EMAIL PROTECTED] > > > > ============================================================== > ============== > ==== > To unsubscribe from this mailing list, please see the > instructions at > http://www.checkpoint.com/services/mailing.html > ============================================================== > ============== > ==== > - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
