1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
12 <title>Status for Andrew DeFaria: DOORS/LOS178 Build Procedure</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/000387.html" title="CVS Adm Web App" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/000388.html" title="CVS Adm Web App - per repository" />
22 <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
26 <div id="container-inner" class="pkg">
29 <div id="banner-inner" class="pkg">
30 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
31 <h2 id="banner-description">Searchable status reports and work log</h2>
36 <div id="pagebody-inner" class="pkg">
38 <div id="alpha-inner" class="pkg">
40 <p class="content-nav">
41 <a href="http://defaria.com/blogs/Status/archives/000387.html">« CVS Adm Web App</a> |
42 <a href="http://defaria.com/blogs/Status/">Main</a>
43 | <a href="http://defaria.com/blogs/Status/archives/000388.html">CVS Adm Web App - per repository »</a>
47 <div class="entry" id="entry-384">
48 <h3 class="entry-header">DOORS/LOS178 Build Procedure</h3>
49 <div class="entry-content">
50 <div class="entry-body">
52 <li>Managed to install DOORS. Turns out that using Tomcat for FlexLM requires port 19360 <b>not</b> port 19353</li>
54 <li>Exported the HybridOS Build Procedure document to create the LOS178 2.1.0 Build Procedure document</li>
56 <li>Attempting to document exactly what CVS access is given for a username in the readers/writers files depending on whether or not either file exists for the CVSAdm web app</li>
59 <div id="more" class="entry-more">
60 <h3>Determining CVS Read/Write Access</h3>
62 <p>CVS decides read/write access based on the presence of the user name in the files readers and writers in the repository. Additionally either or both of these files may be missing.</p>
64 <p>The CVS Manual says:</p>
67 <p>If <tt>readers</tt> exists, and this user is listed in it, then the user gets read-only access. Or if <tt>writers</tt> exists, and this user is <b>not</b> listed in it, then they also get read-only access (this is true even if <tt>readers</tt> exists but they are not listed there). Otherwise, she gets full read-write access.</p>
69 <p>Of course there is a conflict if the user is listed in both files. This is resolved in the more conservative way, it being better to protect the repository too much than too little: such a user gets read-only access.</p>
72 <p>Based on that the following describe the access granted to a user.</p>
75 <table border=1 cellspacing=0 cellpadding=2>
78 <th bgcolor="teal"><font color="white">Case</font></th>
79 <th bgcolor="teal"><font color="white">Readers</font></th>
80 <th bgcolor="teal"><font color="white">Writers</font></th>
81 <th bgcolor="teal"><font color="white">Read Access</font></th>
82 <th bgcolor="teal"><font color="white">Write Access</font></th> </tr>
151 <li>A strict intepretation of the CVS manual might lead you to
152 believe that since readers does not exist and writers does not exist then it would fall into the "Otherwise" statement at the end of the first paragraph. However an argument can be made that the user is also not listed in the writers file because the writers file is not present. But I believe that no access should be granted.</li>
154 <li>Readers does not exist and the user is not listed in writers
155 so read only access.</li>
157 <li>Readers does not exist but the user is listed in writers. So
158 the user has write access. Does this imply read access? Does write-only access exist?</li>
160 <li>User is not listed in the readers file and there is no writers
161 file. This case is not covered by the CVS manual. My assumption is therefore no access. Again a strict interpretation might argue the "Otherwise" clause but I think not.</li>
163 <li>User is not listed in the readers file nor in the writers file
164 therefore read only access.</li>
166 <li>User is not listed in the readers file but is listed in the
167 writers file. User gets read/write access.</li>
169 <li>User is listed in the readers file but there is no writers
170 file. Read only access.</li>
172 <li>User is listed in the readers file but not present in writers
173 file. Read only access.</li>
175 <li>User is listed in the readers file and the writers file. This
176 is the conflict. Resolve the conflict by only providing read access.</li>
180 <p class="entry-footer">
181 <span class="post-footers">Posted by on July 14, 2005 5:13 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000384.html">Permalink</a>