- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCCS total line limit being reached.
Operating System - HP-UX
1753776
Members
7477
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2003 07:34 AM
тАО02-11-2003 07:34 AM
SCCS total line limit being reached.
We are running SCCS for source control on HP/UX 11.0 and seem to be running into a line limitation of 99,999 lines. Is there any way around this limit?
.
Using RCS is not an option for us.
.
Thank you.
.
Using RCS is not an option for us.
.
Thank you.
- Tags:
- SCCS
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2003 08:18 AM
тАО02-11-2003 08:18 AM
Re: SCCS total line limit being reached.
You have a single .c with over 100,000 lines??????
YIKES!
In the old days, all of UNIX was less than that!
Can't you break that into multiple .c's?
Otherwise, you can download a copy of CSSC from GNU (http://www.gnu.org/directory/All_Packages_in_Directory/) and try to hack it to handle more than 99,999 lines, if it caries that same restriction. CSSC is a SCCS clone, and is free.
Good luck,
Vince
YIKES!
In the old days, all of UNIX was less than that!
Can't you break that into multiple .c's?
Otherwise, you can download a copy of CSSC from GNU (http://www.gnu.org/directory/All_Packages_in_Directory/) and try to hack it to handle more than 99,999 lines, if it caries that same restriction. CSSC is a SCCS clone, and is free.
Good luck,
Vince
No matter where you go, there you are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2003 08:22 AM
тАО02-11-2003 08:22 AM
Re: SCCS total line limit being reached.
Thanks Vince.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2003 08:51 AM
тАО02-12-2003 08:51 AM
Re: SCCS total line limit being reached.
As someone else said "Yikes!"
First, are we at 100K lines in edits, or in the actual source?
If the source is huge, then start breaking out those functions into libraries (more .c and .a files for you!) It'd be smart to look and see which functions haven't recently been modified, and move those into
If it's just that the original file has had a LONG history of modifications, it may be time to make a new "version."
Let's say you are on rev. 200 of the .c file. Do an sccsget on -r 198 and save the file.
Do an sccsget on -r 199 and save it as a different name.
Do an sccsget on -r 200 and save it off as a unique name as well.
Now, have your sccs admin RENAME your s.file.c, so you can ADD -r 198 version as a brand new instance of file.c.
Then, check the file out, replace it with -r 199 version, check it in. Do it all over again with version 200.
Congratulations! You now have a file which has only 3 revisions of history, PLUS you can go back to the oldfile.c anytime you please to review other edits without affecting any compilations.
First, are we at 100K lines in edits, or in the actual source?
If the source is huge, then start breaking out those functions into libraries (more .c and .a files for you!) It'd be smart to look and see which functions haven't recently been modified, and move those into
If it's just that the original file has had a LONG history of modifications, it may be time to make a new "version."
Let's say you are on rev. 200 of the .c file. Do an sccsget on -r 198 and save the file.
Do an sccsget on -r 199 and save it as a different name.
Do an sccsget on -r 200 and save it off as a unique name as well.
Now, have your sccs admin RENAME your s.file.c, so you can ADD -r 198 version as a brand new instance of file.c.
Then, check the file out, replace it with -r 199 version, check it in. Do it all over again with version 200.
Congratulations! You now have a file which has only 3 revisions of history, PLUS you can go back to the oldfile.c anytime you please to review other edits without affecting any compilations.
"Any sufficiently advanced technology can be indistinguishable from magic" Arthur C. Clarke. My corollary - "Any advanced technology can be crushed with a sufficently large enough rock."
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP