HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- timestamp of a krsd daemon
Operating System - HP-UX
1833780
Members
2196
Online
110063
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
Go to solution
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
10-04-2005 03:06 AM
10-04-2005 03:06 AM
Hi.
I noticed that, during startup, a line referring the KRS daemon is logged into syslog.log. But its timestamp is not right. See the following lines:
Jun 28 00:26:17 node3 prngd[1539]: have 6 out of 1024 filedescriptors open
Jun 27 18:26:17 node3 krsd[1542]: Delay time is 300 seconds
Jun 27 18:26:17 node3 sfd[1543]: recovering from previous daemon crash.
Jun 28 00:30:39 node3 xntpd[1155]: synchronized to 162.27.18.79, stratum=2
All my boxes have this behaviour.
Is it right ?
I noticed that, during startup, a line referring the KRS daemon is logged into syslog.log. But its timestamp is not right. See the following lines:
Jun 28 00:26:17 node3 prngd[1539]: have 6 out of 1024 filedescriptors open
Jun 27 18:26:17 node3 krsd[1542]: Delay time is 300 seconds
Jun 27 18:26:17 node3 sfd[1543]: recovering from previous daemon crash.
Jun 28 00:30:39 node3 xntpd[1155]: synchronized to 162.27.18.79, stratum=2
All my boxes have this behaviour.
Is it right ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2005 03:17 AM
10-04-2005 03:17 AM
Solution
Cas,
Check this doc.
Title: syslogd writes messages from krsd and sfd with wrong timestamp
Document ID: KBRC00010240
US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910694
Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910694
Regards,
Robert-Jan
Check this doc.
Title: syslogd writes messages from krsd and sfd with wrong timestamp
Document ID: KBRC00010240
US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910694
Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910694
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2005 08:10 AM
10-04-2005 08:10 AM
Re: timestamp of a krsd daemon
thank you
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