HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- can remshd log into syslog?
Operating System - HP-UX
1834210
Members
2362
Online
110066
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-20-1999 11:13 PM
12-20-1999 11:13 PM
can remshd log into syslog?
I need to know if it is possible to get the remshd to log info into the
syslog. I have alot of files being rcp'ed into one server, and I need to know
what filenames are being rcp'ed in, which server any particular file is coming
from, and what remote user is sending the file. Right now, the inetd is
logging incoming connections only by server name and date. The man pages are
pretty blank on this, and nothing else is out on the web. Any help out there?
Thanks
-Jeff Kilgore
syslog. I have alot of files being rcp'ed into one server, and I need to know
what filenames are being rcp'ed in, which server any particular file is coming
from, and what remote user is sending the file. Right now, the inetd is
logging incoming connections only by server name and date. The man pages are
pretty blank on this, and nothing else is out on the web. Any help out there?
Thanks
-Jeff Kilgore
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-1999 08:28 AM
12-21-1999 08:28 AM
Re: can remshd log into syslog?
If the amount of info you want is more than syslog can give you (in this case
file names etc sounds like it is) you can do something like what I once did to
ftp. Its a bit messy but it works and you can use it as a starying point
#!/bin/sh
# Desc: Logs all ftp commands and time
LOGFILE=/var/adm/ftp/ftp.log
echo "`whoami` on `uname -n` opts : $@ \nStart ftp : `date`">> $LOGFILE
/usr/bin/ftp $@
echo "End ftp : `date`">> $LOGFILE
echo "\n">> $LOGFILE
You should add some traps and make it a bit smarter but you can get the general
jist of it I think. basically its just a wrapper for the command and you can
store some or all the info issued to it. Just replace the original command
with this one and rename the original command.
regards,
AG
file names etc sounds like it is) you can do something like what I once did to
ftp. Its a bit messy but it works and you can use it as a starying point
#!/bin/sh
# Desc: Logs all ftp commands and time
LOGFILE=/var/adm/ftp/ftp.log
echo "`whoami` on `uname -n` opts : $@ \nStart ftp : `date`">> $LOGFILE
/usr/bin/ftp $@
echo "End ftp : `date`">> $LOGFILE
echo "\n">> $LOGFILE
You should add some traps and make it a bit smarter but you can get the general
jist of it I think. basically its just a wrapper for the command and you can
store some or all the info issued to it. Just replace the original command
with this one and rename the original command.
regards,
AG
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