Re: Limitation on --allow-root pserver options?

2003-12-02 Thread Larry Jones
Mark writes:
> 
> Currently we have 58 --allow-root options setup in the wrapper script.

Why do you have so many separate repositories?  Can't you just use
modules in a single repository?

> Is this a solaris limitation or a cvs limitation (there are about 2513
> characters that make up the --allow-root argument string, excluding any
> spaces)?

There is no limit in CVS.

-Larry Jones

The authorities are trying to silence any view contrary to their own!
-- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Limitation on --allow-root pserver options?

2003-12-02 Thread David Wood
You could consider using xinetd alongside Solaris inetd (just for the CVS 
port). It would be a simple experiment to set it up and see if it, too, 
exhibits the problem. 

[EMAIL PROTECTED] wrote on 12/02/2003 
03:38:25 AM:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Mark <[EMAIL PROTECTED]> writes:
> 
> > We have cvs pserver 1.11.1p1 setup on solaris 2.8 and a wrapper script
> > in /etc/inetd.conf to allow many --allow-roots (we have many
> > apps/groups/business units we provide CM support for, thus the need to
> > many repos). We use WinCVS 1.3 for the client.
> 
> Okay. However, there are many bug fixes to cvs available in the latest
> cvs 1.11.9 version of cvs.
> 
> > Currently we have 58 --allow-root options setup in the wrapper script.
> > The 58th --allow-root does not work/is not recognized.
> > 
> > When we try to login via pserver:
> > - the client gets "no such repository" message
> > - the server logs a "login refused for" in /var/adm/messages 
> > 
> > When I moved that 58th -allow-root to the top of the -allow-root list,
> > it worked, but then the new last one in the list, now has the above
> > described issues.
> 
> Well, clearly some problem is being uncovered. If you are able to
> upgrade to a newer version of cvs and still have the problem, then
> it may be possible to help you debug the problem on this list.
> 
> > Is this a solaris limitation or a cvs limitation (there are about 2513
> > characters that make up the --allow-root argument string, excluding 
any
> > spaces)?
> 
> I am not aware of such a limitation, however, you could test it 
yourself.
> Take a simple program like this:
> 
> % cat testit.c
> #include 
> int main(int argc, char *argv[]) {
> int i; for ( i = 0; i < argc; i++ ) printf("%d: %s\n", i, argv[i]);
> return(0);
> }
> %
> 
> Compile it and give it all of the arguments you setup in your wrapper
> script for cvs and see what happens.
> 
> > I could use different ports on the server to balance out the
> > repositories but WinCVS 1.3 doesn't retain port info inside the
> > CVS admin subdirectory files in the workares which causes problems
> > for users who have to work out of repos on different ports at the same
> > time. (ie. instead of WinCVS 1.3 gathering all it needs from a
> > workarea's CVS subdir to commit/update etc... it uses the current port
> > settings in the WinCVS preferences regardless of what the workarea is
> > currently being used this is quite annoying and confusing)... if
> > this issues has been fixed in WinCVS 1.3, please let me know.
> > 
> > Any help/insight/suggestions is appreciated. yes we only have one
> > solaris server to use, and yes we must have independent
> > repositories..
> > 
> > Thanks,
> > 
> > Mark
> 
>Good luck,
>-- Mark
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (FreeBSD)
> 
> iD8DBQE/zE+B3x41pRYZE/gRAsJMAJsGOsCUaYAUE++6sIWazSnGfHTV9ACdFVck
> Lyqb6jf6h+thjyzNIlIJkUY=
> =3nB/
> -END PGP SIGNATURE-
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Limitation on --allow-root pserver options?

2003-12-02 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Mark <[EMAIL PROTECTED]> writes:

> We have cvs pserver 1.11.1p1 setup on solaris 2.8 and a wrapper script
> in /etc/inetd.conf to allow many --allow-roots (we have many
> apps/groups/business units we provide CM support for, thus the need to
> many repos). We use WinCVS 1.3 for the client.

Okay. However, there are many bug fixes to cvs available in the latest
cvs 1.11.9 version of cvs.

> Currently we have 58 --allow-root options setup in the wrapper script.
> The 58th --allow-root does not work/is not recognized.
> 
> When we try to login via pserver:
> - the client gets "no such repository" message
> - the server logs a "login refused for" in /var/adm/messages 
> 
> When I moved that 58th -allow-root to the top of the -allow-root list,
> it worked, but then the new last one in the list, now has the above
> described issues.

Well, clearly some problem is being uncovered. If you are able to
upgrade to a newer version of cvs and still have the problem, then
it may be possible to help you debug the problem on this list.

> Is this a solaris limitation or a cvs limitation (there are about 2513
> characters that make up the --allow-root argument string, excluding any
> spaces)?

I am not aware of such a limitation, however, you could test it yourself.
Take a simple program like this:

% cat testit.c
#include 
int main(int argc, char *argv[]) {
int i; for ( i = 0; i < argc; i++ ) printf("%d: %s\n", i, argv[i]);
return(0);
}
%

Compile it and give it all of the arguments you setup in your wrapper
script for cvs and see what happens.

> I could use different ports on the server to balance out the
> repositories but WinCVS 1.3 doesn't retain port info inside the
> CVS admin subdirectory files in the workares which causes problems
> for users who have to work out of repos on different ports at the same
> time. (ie. instead of WinCVS 1.3 gathering all it needs from a
> workarea's CVS subdir to commit/update etc... it uses the current port
> settings in the WinCVS preferences regardless of what the workarea is
> currently being used this is quite annoying and confusing)... if
> this issues has been fixed in WinCVS 1.3, please let me know.
> 
> Any help/insight/suggestions is appreciated. yes we only have one
> solaris server to use, and yes we must have independent
> repositories..
> 
> Thanks,
> 
> Mark

Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/zE+B3x41pRYZE/gRAsJMAJsGOsCUaYAUE++6sIWazSnGfHTV9ACdFVck
Lyqb6jf6h+thjyzNIlIJkUY=
=3nB/
-END PGP SIGNATURE-


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Limitation on --allow-root pserver options?

2003-12-02 Thread Mark

We have cvs pserver 1.11.1p1 setup on solaris 2.8 and a wrapper script in
/etc/inetd.conf to allow many --allow-roots (we have many apps/groups/business
units we provide CM support for, thus the need to many repos). We use WinCVS
1.3 for the client.

Currently we have 58 --allow-root options setup in the wrapper script. The 58th
--allow-root does not work/is not recognized.

When we try to login via pserver:
- the client gets "no such repository" message
- the server logs a "login refused for" in /var/adm/messages 

When I moved that 58th -allow-root to the top of the -allow-root list, it
worked, but then the new last one in the list, now has the above described
issues.

Is this a solaris limitation or a cvs limitation (there are about 2513
characters that make up the --allow-root argument string, excluding any
spaces)?

I could use different ports on the server to balance out the repositories
but WinCVS 1.3 doesn't retain port info inside the CVS admin subdirectory files
in the workares which causes problems for users who have to work out of
repos on different ports at the same time. (ie. instead of WinCVS 1.3
gathering all it needs from a workarea's CVS subdir to commit/update etc... it
uses the current port settings in the WinCVS preferences regardless of what the
workarea is currently being used this is quite annoying and confusing)...
if this issues has been fixed in WinCVS 1.3, please let me know.

Any help/insight/suggestions is appreciated. yes we only have one solaris
server to use, and yes we must have independent repositories..

Thanks,

Mark



__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs