HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error in hp Secure shell
Operating System - HP-UX
1833694
Members
3576
Online
110062
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
Forums
Discussions
Discussions
Discussions
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
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
09-30-2008 01:43 AM
09-30-2008 01:43 AM
Error in hp Secure shell
Hi,
I have installed 11.31 installed on of my box have also the latest hp secure
Secure_Shell A.05.10.008 HP-UX Secure Shell
but when the wtmps file is full the ssh connection will be getting very very slow any one have any idea.
Thanks,
Avinash
I have installed 11.31 installed on of my box have also the latest hp secure
Secure_Shell A.05.10.008 HP-UX Secure Shell
but when the wtmps file is full the ssh connection will be getting very very slow any one have any idea.
Thanks,
Avinash
Great Power Comes With Great Responsibility
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2008 03:31 AM
09-30-2008 03:31 AM
Re: Error in hp Secure shell
Hi Avinash,
I don't think there is any connection between ssh shell and wtmp, The only connection is if the user is login successfully then one entry will be there in wtmp, better you check some other things.
One more things there is no limit for wtmp how you judge that wtmp file is getting full?
Suraj
I don't think there is any connection between ssh shell and wtmp, The only connection is if the user is login successfully then one entry will be there in wtmp, better you check some other things.
One more things there is no limit for wtmp how you judge that wtmp file is getting full?
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2008 06:10 AM
09-30-2008 06:10 AM
Re: Error in hp Secure shell
The man page for wtmps says:
"Note that wtmps and btmps tend to grow without bound, and should be checked regularly. Information that is no longer useful should be removed periodically to prevent the file from becoming too large.
Also note that wtmps and btmps are not created by the programs that maintain them. Thus, if these files are removed, login record-keeping is turned off."
Managing the system log files (including the wtmps file) is a part of normal maintenance tasks for any Unix sysadmin. Of course, it can be automated if you wish.
The simplest way would be to set up a cron job to copy the current wtmps file to archive location and then truncate the original file to zero size. The archived files can then be compressed with gzip for long-term storage, or simply deleted when they are old enough.
Find out your site's data retention policies: how long should information about old logins be stored? Four weeks, a number of months, or a number of years?
And how fast does the wtmps file grow in your system?
Then write a script and set it up as a cron job so that the current wtmps file is truncated often enough to keep its size manageable, and the archive location will hold the correct amount of older versions of the file to comply with your site policy.
Make this a part of your standard procedure for setting up a new machine.
If someone needs to read the older login information, he/she can use the "-f" option of the "last" command to look into one of the archived files instead of the current wtmps file.
MK
"Note that wtmps and btmps tend to grow without bound, and should be checked regularly. Information that is no longer useful should be removed periodically to prevent the file from becoming too large.
Also note that wtmps and btmps are not created by the programs that maintain them. Thus, if these files are removed, login record-keeping is turned off."
Managing the system log files (including the wtmps file) is a part of normal maintenance tasks for any Unix sysadmin. Of course, it can be automated if you wish.
The simplest way would be to set up a cron job to copy the current wtmps file to archive location and then truncate the original file to zero size. The archived files can then be compressed with gzip for long-term storage, or simply deleted when they are old enough.
Find out your site's data retention policies: how long should information about old logins be stored? Four weeks, a number of months, or a number of years?
And how fast does the wtmps file grow in your system?
Then write a script and set it up as a cron job so that the current wtmps file is truncated often enough to keep its size manageable, and the archive location will hold the correct amount of older versions of the file to comply with your site policy.
Make this a part of your standard procedure for setting up a new machine.
If someone needs to read the older login information, he/she can use the "-f" option of the "last" command to look into one of the archived files instead of the current wtmps file.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2009 03:53 AM
03-01-2009 03:53 AM
Re: Error in hp Secure shell
.
Great Power Comes With Great Responsibility
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP