Sponsored Content
Full Discussion: NFS problems (Debian)
Operating Systems Linux Debian NFS problems (Debian) Post 302282289 by Neo on Friday 30th of January 2009 01:03:35 PM
Old 01-30-2009
identd is a process that typically runs out of your inetd server. It keeps track of what user is running what TCP service, and then reports this to whoever requests it. I don't recall if it is required for NFS, so this might be off track..... if it is, I apologize.


Quote:
Many people misunderstand the usefulness of identd, and so disable it or block all off site requests for it. identd is not there to help out remote sites. There is no way of knowing if the data you get from the remote identd is correct or not. There is no authentication in identd requests.

Why would you want to run it then? Because it helps you out, and is another data-point in tracking. If your identd is not compromised, then you know it's telling remote sites the user-name or UID of people using TCP services. If the admin at a remote site comes back to you and tells you user so-and-so was trying to hack into their site, you can easily take action against that user. If you are not running identd, you will have to look at lots and lots of logs, figure out who was on at the time, and in general take a lot more time to track down the user.

The identd that ships with most distributions is more configurable than many people think. You can disable it for specific users (they can make a .noident file), you can log all identd requests (We recommend it), you can even have identd return a UID instead of a user name or even NO-USER.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS server problems [merged]

I have a machine A NFS mounted on machine B I am doing a build from machine B on the MFS mounted dir of machine A but I keep getting the following: NFS server A not responding still trying. I go to machine A and can log onto machine A and everything seems fine. How do I go about finding... (6 Replies)
Discussion started by: brv
6 Replies

2. UNIX for Dummies Questions & Answers

SCO NFS problems

Hi, I've got a really old system we use for call logging. The OS is SCO 3.2 uname -a output SCO_SV bts7053 3.2 2 i386 the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are... (1 Reply)
Discussion started by: johno12345
1 Replies

3. UNIX for Dummies Questions & Answers

nfs mount and links removal problems.

Ok, so I have an nfs mount setup and within it there are symbolic links to other directories and such. So anyways I created a link to a directory like so ln -s /var/stuff/more/stuff/here/ stuff/ and i ended up with directory stuff with link 'here' inside. so i was pieved and decided... (1 Reply)
Discussion started by: VRoemer
1 Replies

4. UNIX for Advanced & Expert Users

NFS Problems

I am having a really bad day today. I am trying to get an nfs mount to work. I want to have a mount from machinea:/home going to /home on machineb. I can mount machinea:/home on any mount point EXCEPT /home and see the files. I can not see the files or list the directory (it hangs) when I mount... (17 Replies)
Discussion started by: mbathrick
17 Replies

5. Solaris

Having problems starting up NFS on an OpenSolaris box

I am trying to set up an OpenSolaris box to be an NFS server. The OpenSolaris version is 2008.11. The kernel (uname -a output) is: SunOS minime-28 5.11 snv_101b i86pc i386 i86pc It is running ZFS but I know nothing about ZFS. I have an entry in the /etc/dfs/dfstab file: share -F... (1 Reply)
Discussion started by: sqa777
1 Replies

6. Debian

Debian Lenny update problems

Hi everybody! I have a very big problem, I can not make any updates on my debian lenny. I get everytime this errors with apt-get update: Err http://security.debian.org lenny/updates Release.gpg Connection failed Err http://www.backports.org lenny-backports Release.gpg Connection... (2 Replies)
Discussion started by: magge
2 Replies

7. AIX

NFS mount problems on AIX

Hi, I have two machines (AIX) each on a different VLAN. Need to mount a filesystem using nfs on the other one. When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Discussion started by: aixromeo
6 Replies

8. Red Hat

NFS problems

Hi All, I hoping someone can help me get my NFS working properly. I don't know why I'm having little issues... Overall, NFS is working, therefore, the problem may not be with NFS. I can ssh to remote nodes and view NFS shared directories (/home). Here is the problem, when on a node and I open a... (2 Replies)
Discussion started by: Bic121
2 Replies

9. Red Hat

Memory problems in NFS client server

Hi all, i have some doubts in a situation that i fail to get an answer in Google. I have a solaris 10 nfs server and 5 centos 6.0 nfs clients. The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies
POE::Component::Client::Ident(3pm)			User Contributed Perl Documentation			POE::Component::Client::Ident(3pm)

NAME
POE::Component::Client::Ident - A component that provides non-blocking ident lookups to your sessions. SYNOPSIS
use POE::Component::Client::Ident; my $poco_obj = POE::Component::Client::Ident->spawn ( 'Ident-Client' ); $kernel->post ( 'Ident-Client' => query => Socket => $socket ); $kernel->post ( 'Ident-Client' => query => PeerAddr => '10.0.0.1', PeerPort => 2345, SockAddr => '192.168.1.254', SockPort => 6669, BuggyIdentd => 1, TimeOut => 30 ); DESCRIPTION
POE::Component::Client::Ident is a POE component that provides non-blocking Ident lookup services to other components and sessions. The Ident protocol is described in RFC 1413 <http://www.faqs.org/rfcs/rfc1413.html>. The component takes requests in the form of events, spawns POE::Component::Client::Ident::Agent sessions to perform the Ident queries and returns the appropriate responses to the requesting session. CONSTRUCTOR
spawn Takes one argument, a kernel alias to christen the new component with. Returns an object. METHODS
These methods are available on the poco object returned by spawn(). session_id Returns the component's session ID. shutdown Takes no arguments. Causes the component to terminate gracefully. Any pending Ident::Agent components that are running will be closed without returning events. INPUT
The component accepts the following events: query Takes either the arguments: "PeerAddr", the remote IP address where a TCP connection has originated; "PeerPort", the port where the TCP has originated from; "SockAddr", the address of our end of the connection; "SockPort", the port of our end of the connection; OR: "Socket", the socket handle of the connection, the component will work out all the details for you. If Socket is defined, it will override the settings of the other arguments. See the documentation for Ident-Agent for extra parameters you may pass. shutdown Takes no arguments. Causes the component to terminate gracefully. Any pending Ident::Agent components that are running will be closed without returning events. OUTPUT
The events you can expect to receive having submitted a 'query'. All the events returned by the component have a hashref as ARG0. This hashref contains the arguments that were passed to the component. If a socket handle was passed, the hashref will contain the appropriate PeerAddr, PeerPort, SockAddr and Sock Port. ident_client_reply Returned when the component receives a USERID response from the identd. ARG0 is hashref, ARG1 is the opsys field and ARG2 is the userid or something else depending on whether the opsys field is set to 'OTHER' ( Don't blame me, read the RFC ). ident_client_error Returned when the component receives an ERROR response from the identd, there was some sort of communication error with the remote host ( ie. no identd running ) or it had some other problem with making the connection to the other host. No matter. ARG0 is hashref, ARG1 is the type of error. AUTHOR
Chris Williams, <chris@bingosnet.co.uk<gt> SEE ALSO
RFC 1413 <http://www.faqs.org/rfcs/rfc1413.html> POE::Component::Client::Ident::Agent perl v5.8.8 2007-10-31 POE::Component::Client::Ident(3pm)
All times are GMT -4. The time now is 11:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy