Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 527
  • Last Modified:

chmod and Sun Workshop Teamware

I'm using sccs commands with Sun Workshop Teamware.  I have Unix scripts that I have written for C shell.

How do I configure the file under sccs so that it retains execuatble permissions when I check the file out, and then back in?

Currently I'm doing a chmod +x every time I check the file back in because sccs (at least for now) removes the execute permissions (similar to chmod 444)
0
lhgarrett
Asked:
lhgarrett
  • 7
  • 6
1 Solution
 
jlevieCommented:
It looks to me that if you change the mode of the sccs file (chmod ugo+x SCCS/s.some-file), then from then on the file will check out as executable.
0
 
cartoon022100Commented:
Hi,
As you said the execute permissions will not be retained once you check out
A silly answer i can suggest you now to avoid "chmod +x" every time is to write a wrapper or a shell script or a perl script to do the chmod +x for you every time.

This is what i follow now.I also faced the same problem like u.Now the chmod is done automatically by my script every time whne i check out.


Regards,
Inigo


0
 
jlevieCommented:
Not so fast cartoon... I've just checked what I suggested with Teamware and the executable mode is preserved across checkin/checkout cycles. If your instance is not behaving that way it sounds like an sccs or Teamware bug. Is your's up to date patch wise?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
lhgarrettAuthor Commented:
> write a script to do the chmod +x for you every time

I'd like to allow sccs to maintain the executable mode on a file-by-file basis for me. Ideally, I should only have to set the mode once.
0
 
lhgarrettAuthor Commented:
> chmod ugo+x SCCS/s.some-file

Is there an sccs command (or a workspace command) that I should use to perform this function?
0
 
jlevieCommented:
I can't find any sccs command that will do it, nor can I find any way from within Workshop to do it. What I did was to use a terminal window and cd to the "Workspace" directory and run the "chmod ugo +x SCCS/s.some-file" there.

One other thing to note is that if the file is executable when it is first checked in, it retains that mode.
0
 
lhgarrettAuthor Commented:
> If your instance is not behaving that way it sounds like an sccs or Teamware bug

My version of sccs only retains the permissions on the SCCS/s.* files. The actual files' execute permission is destroyed (on delget or unedit). I get the same problem from the Teamware GUI, or if I checkout and checkin on the commandline with the following commands:

    % sccs edit filename
    % sccs delget filename

How can I determine which version of sccs I'm using. When I do help from Teamware, I get:

   Teamware 2.0 10/31/96

What version are you using? Thanks!
0
 
jlevieCommented:
Mine is Teamware 2.1 12/15/98 on Solaris 2.7. Relevant patches installed include:

106748-04 - /usr/ccs/bin/sccs and /usr/ccs/bin/make patch
107354-01 - Patch for Teamware 21

So far as I know you can't ask sccs for it's version. Which Solaris are you using? Knowing the version I can tell you what sccs and Teamware patches exist.
0
 
lhgarrettAuthor Commented:
I am running Solaris 2.6:

   % uname -X
   System = SunOS
   Release = 5.6
   KernalID = Generic_105181-05

Thanks!
   
0
 
jlevieCommented:
I haven't forgotten about this. I've managed to duplicate your problem on a 2.6 system. The interesting thing is that it looks like it may not actually be an sccs problem. I can use the binaries from a 2.7 system (export /usr/ccs from 2.7 where it works correctly & nfs mount it on 2.6) and still have the problem. The only thing that I can see at this point that might explain it is some difference in libc between 2.6 & 2.7.

More soon, I hope...
0
 
jlevieCommented:
I've done everything that I can think of, including bringing a 2.6 box totally up to date w/respect to patches. It just simply doesn't work there. And I found that it doesn't always work on 2.7.

I have found that I can make it work every time on both 2.6 and 2.7 by using sccs binaries from the Solaris 8 beta distribution. As far as I can tell right now, there are no unwelcome side affects from doing so, but obviously I can't make any guarantees.

Hmm, seems like a bug report/feature request to Sun might be in order.
0
 
lhgarrettAuthor Commented:
> I've done everything that I can think of, including bringing a 2.6 box totally up to date w/respect to patches

Thanks! I guess that's the way it is... If you have the ability to (or desire to ) write a bug report, I appreciate it.

In the mean time it's appropriate to award points for all of you hard research! Thanks again!
0
 
jlevieCommented:
I'm in the process of filling a bug report. The initial response was "sccs can't do that, see bug ID nnnnn". Then when I explained that it works in Solaris 8 and that the binaries from 8 worked properly on 2.6 & 2.7, there was this really long pause and an "let me check on that and call you back", so we'll see.
0
 
lhgarrettAuthor Commented:
> I'm in the process of filling a bug report

Thanks, I'm glad they are checking into it... From a user's perspective, persistence of execute permissions across checkin/checkout is about as basic as it gets; it should be supported.  :-)
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now