- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- esm and server log down
Operating System - HP-UX
1825512
Members
1907
Online
109681
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
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
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
тАО01-22-2008 07:08 AM
тАО01-22-2008 07:08 AM
esm and server log down
Hi,
I have been alerted by a security application ESM and I am not too sure some of the procs stated whether I should remove them from inetd:
how can I determine what nd when used the following protocols:
exec
login
and also I have a snmpdm process alerted, what can i expect to use SNMP from a system point ie service guard maybe?
Thanks
Chris
I have been alerted by a security application ESM and I am not too sure some of the procs stated whether I should remove them from inetd:
how can I determine what nd when used the following protocols:
exec
login
and also I have a snmpdm process alerted, what can i expect to use SNMP from a system point ie service guard maybe?
Thanks
Chris
hello
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2008 09:58 AM
тАО01-22-2008 09:58 AM
Re: esm and server log down
exec and login have been configured as well as .rhosts for cluster services (i believe) therefore these protocols are required.
hello
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2008 02:20 PM
тАО01-22-2008 02:20 PM
Re: esm and server log down
Hello,
a) I know ESM. I introduced it to a large
telco last year :)
b) Firstly, enable inetd logging, by adding
'-l' to the start up file. The command 'inetd
-l' will enable logging for a running inetd
process, so no need to stop inetd when making
these changes.
c) Then set up access control list through
/var/adm/inetd.sec.
d) You can even get hold of logdaemon from Wietse site at http://www.porcupine.org/
Logdaemon contains many useful utilities,
however some people have had problems
compiling them with the HP authentication
libraries. Fortunately rexecd is an exception. You can compile it and replace
the standard one that HP-UX ships.
Logdaemon provides much better logging
capabilities. In old times, I used it
for rsh/remsh protocols to capture
the command that was executed from remote
servers :)
Regarding SNMP: do you have any
monitoring (like OpenView, BMC Patrol,
CA Unicentre) on your servers?
Cheers,
VK2COT
a) I know ESM. I introduced it to a large
telco last year :)
b) Firstly, enable inetd logging, by adding
'-l' to the start up file. The command 'inetd
-l' will enable logging for a running inetd
process, so no need to stop inetd when making
these changes.
c) Then set up access control list through
/var/adm/inetd.sec.
d) You can even get hold of logdaemon from Wietse site at http://www.porcupine.org/
Logdaemon contains many useful utilities,
however some people have had problems
compiling them with the HP authentication
libraries. Fortunately rexecd is an exception. You can compile it and replace
the standard one that HP-UX ships.
Logdaemon provides much better logging
capabilities. In old times, I used it
for rsh/remsh protocols to capture
the command that was executed from remote
servers :)
Regarding SNMP: do you have any
monitoring (like OpenView, BMC Patrol,
CA Unicentre) on your servers?
Cheers,
VK2COT
VK2COT - Dusan Baljevic
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP