Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-08-2001 03:16 AM
08-08-2001 03:16 AM
SCCS
- Tags:
- SCCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2001 06:52 AM
08-08-2001 06:52 AM
Re: SCCS
Use sccs on cronjobs, if more than one person is going to edit it. Or if that's audit requirement.
To create new SCCS file use
#sccs create root-cronjob
To get file for editing use
#sccs edit root-cronjob
edit it using vi/ex...
To submit changes to SCCS and get new version use
#sccs delget root-cronjob.
Check man sccs.
Thanks.
Prashant Deshpande.
- Tags:
- crontab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2001 09:23 AM
08-08-2001 09:23 AM
Re: SCCS
Reason number two to keep past versions: You accidentally delete the crontab file for root instead of modifying it. Or you forget what change you put in 10 weeks ago.
I never edit the crontab file directory. Instead I do this....
1.crontab -l > root.14Feb2001
2. ls -ltr root.* <--to find the last mod.
3. diff root.14Feb2001 root.02Feb2001
This makes sure no one was modifying the file since the last time I documented the mod.
4. vi root.14Feb2001 and make my changes
5. diff root.14Feb2001 root.02Feb2001 <--verifies I made the correct mods.
6. crontab root.14Feb2001
Hope this helps. steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2001 06:22 PM
08-08-2001 06:22 PM
Re: SCCS
script. SCCS will clear the executable flag on checkin.
The first line is
#!/bin/crontab.
I edit this file and then run it. Then I can submit it to
RCS.
Alternatively you can have the script use a here
document and the submit itself. Try something
like this for SCCS.
#!/bin/sh
/bin/crontab << EOF
... cronjobs go here
EOF
sccs put $0
sccs get $0
chmod +x $0
# EOF
You edit the cron entries in the script then run it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2001 07:27 PM
08-08-2001 07:27 PM
Re: SCCS
We use 'rcs' to do all of our version control.
It is used for sytsem configuration files and
scripts, including 'cron'
We find it far easier than 'sccs'. Attached is
an example of how to use it.
HTH
-Michael