FINGERD - An implementation of the 'finger' protocol for Novell Netware. DESCRIPTION Allows a user on a TCP/IP network to finger a user or list users at a Novell Netware machine. FEATURES Data is returned in pretty much Unix standard finger format. The output looks like this... (The '>' is there to make it clear that it's not part of my text.) >[storm.sitename.com] >Login Name TTY When Where >supervisor System Manager 001 Fri 16:51 00800F78C646A4 >supervisor System Manager 002 Mon 22:25 0000C067C646A4 >chuck Chuck Farley 003 Tue 18:28 00AA002FC646A4 First is the username, followed by the users full name. The TTY field is actually the connection number for each process. The 'When' field is the login time, and the Where is the hardware network address of each connection. This portion can be disabled by loading FINGERD with the OFF option. "LOAD FINGERD OFF" would start it up with the ability to finger users, but not get a list of all the users currently on the site. When individual users are fingered, it looks for their projects and plans in a directory named SYS:\MAIL\\_PROJECT and SYS:\MAIL\\PLAN. The 'bind_id' is the bindery object ID of each individual user. It's not a perfect solution, but since it was designed for 3.11, I *know* that directory is there in 3.11. This is what fingering 'supervisor@storm.sitename.com' looks like: (Again, '>' for machine-generated text.) >[storm.sitename.com] >Login name: supervisor In real life: System Manager >Currently logged in from 00800F780480 >Project: MHS-programming, of course... >Plan: >Plan? I don't need no stinking plan! > >Ahhh, maybe I do anyway. And for users that don't exist on your machine... >[storm.sitename.com] >Login name: nobody In real life: ??? REQUIREMENTS Novell Netware 3.11 or above. (I'm not sure how it'll run under Bindery Emulation on a 4.01 machine...) FILES The locations for the ersatz '.plan' and '.project' files are: .plan: SYS:\MAIL\\_PLAN .project: SYS:\MAIL\\_PROJECT BUGS It does NOT support finger-through. (i.e. you cannot finger user@site1@site2. The normal use of this is if your site cannot directly finger site1, but site2 can. It makes a request of site2 to finger user@site1. Normally these can be chained (user@site1@site2@site3). The only users that can be fingered, however, are the users directly listed on the site running the program. If there's enough request for it, I may put in a configuration file, allowing the specification of a directory under which each user has a directory and in that is the PLANS and PROJECTS. I personally don't see it as that serious a need, though. If I'm wrong, I'm willing to be corrected. PAYMENT I'm a big believer in the concepts of free software, shareware, and even public domain software, so spread the program around. If you want the source, well, it's un-pretty, but it does use a bunch of Netware API calls that are useful to learn more about. (After all, I used this to learn how!) Send me a SASE and some chocolate, or whatever, and I'll send it off to you. (Or I can the send the source via email.) If you do use the program (binary or source), at home, in business, whatever, please send me a postcard at: Morgan Schweers 1562 Bittern Drive Sunnyvale, CA 94087 CONTACT mrs@netcom.com. I am the sole 'support' for this program. It shouldn't take much support, though... I'm not going to be able to dedicate much effort to supporting it. -- Morgan Schweers