HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Multiple /dev/log sockets with syslogd - for chroo...
Operating System - HP-UX
1828267
Members
3231
Online
109975
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
12-18-2006 11:26 PM
12-18-2006 11:26 PM
Multiple /dev/log sockets with syslogd - for chroot environments
Hi, I'm using sftp in a chroot environment, and logging the transfers with the LogSftp yes option in sshd_config.
This logging works fine in normal sftp transfers, but doesn't when running sftp to a chroot user. In Linux this can be fixed by passing "-a /chroot/path/var/log" to syslogd to give it an extra socket to read from, however hpux only seems to have a -p switch to allow "an alternative" socket rather than multiple.
Is there any way to achieve this with hpux syslogd? I don't think running multiple syslogd's is the answer since we'll likely get duplicate messages from the kernel etc.
The syslog requirement is detailed here: -
http://sftplogging.sourceforge.net/download/README
But as said this works on Linux but not on HPUX from what I can see.
This logging works fine in normal sftp transfers, but doesn't when running sftp to a chroot user. In Linux this can be fixed by passing "-a /chroot/path/var/log" to syslogd to give it an extra socket to read from, however hpux only seems to have a -p switch to allow "an alternative" socket rather than multiple.
Is there any way to achieve this with hpux syslogd? I don't think running multiple syslogd's is the answer since we'll likely get duplicate messages from the kernel etc.
The syslog requirement is detailed here: -
http://sftplogging.sourceforge.net/download/README
But as said this works on Linux but not on HPUX from what I can see.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2006 11:54 PM
12-18-2006 11:54 PM
Re: Multiple /dev/log sockets with syslogd - for chroot environments
Simon,
from the ssh guide:
"In a chroot-ed environment, users do not see a subset of syslogmessages. HP-UX Secure Shell writes syslog messages at the time of authentication and when the session is terminated. The syslogddaemon reads the syslog messages written by all subsystems andreports it to the /dev/log file. In a chroot-ed environment, the sshddaemon writes its syslog messages to/dev/log. It is notpossible to link the /dev/log file to the /dev/log file,resulting in users not being able to view the subset of syslogmessages.Workaround: There is no workaround for this problem. Users of chroot-ed HP-UX Secure Shell environments must be aware that a subset of messages written by the sshd daemon will not show up in syslog."
So I read this that it is not possible.
from the ssh guide:
"In a chroot-ed environment, users do not see a subset of syslogmessages. HP-UX Secure Shell writes syslog messages at the time of authentication and when the session is terminated. The syslogddaemon reads the syslog messages written by all subsystems andreports it to the /dev/log file. In a chroot-ed environment, the sshddaemon writes its syslog messages to
So I read this that it is not possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2006 09:09 PM
12-19-2006 09:09 PM
Re: Multiple /dev/log sockets with syslogd - for chroot environments
Simon,
thanks for the points.
"4- 7: The answer helped with a portion of my question, but I still need some additional help!"
What part of the question do you need further help with ? Please keep the thread updated, so people can respond quickly.
thanks for the points.
"4- 7: The answer helped with a portion of my question, but I still need some additional help!"
What part of the question do you need further help with ? Please keep the thread updated, so people can respond quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2006 10:31 PM
12-20-2006 10:31 PM
Re: Multiple /dev/log sockets with syslogd - for chroot environments
Hi
I didn't give a "The answer has solved my problem completely! Now I'm a happy camper!" because it's still technically possible for someone to come up with ideas or workarounds - the present answer is so defeatist :D Whilst that document says it's not possible, that document clearly applies to the HPUX syslogd since it is a restriction of that particular implementation of syslog that can only read from one /dev/log.
Someone for example may report that they have compiled and used GNU syslogd for example, or used some third-party tool or script that can read messages from /newroot/dev/log socket and replicate them into the real /dev/log.
Have some more points anyway :D
I didn't give a "The answer has solved my problem completely! Now I'm a happy camper!" because it's still technically possible for someone to come up with ideas or workarounds - the present answer is so defeatist :D Whilst that document says it's not possible, that document clearly applies to the HPUX syslogd since it is a restriction of that particular implementation of syslog that can only read from one /dev/log.
Someone for example may report that they have compiled and used GNU syslogd for example, or used some third-party tool or script that can read messages from /newroot/dev/log socket and replicate them into the real /dev/log.
Have some more points anyway :D
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP