Good idea, Michael. That would work if the once-a-day restriction doesn't
hamper Justin's requirements too much. But if you're taking that approach,
it's not much more work to write, say, a perl app that would go into the
relevant files, parse the info, and put it into a delimited database. Then a
separate app would search it. Should all run a bit slicker than just
redirecting finger then grep'ing lines (which approach also requires a bit
more fiddling than is initially obvious).
The real issues for Justin are:
1. Would a database that's as much as a day out of date present a problem?
2. Do his requirements include being able to request this info remotely, as
finger makes possible?
3. His original posting mentioned additional e-mail accounts. How does he
want those to show up in the sort of search he is attempting to implement?
4. Who has to be able to do these searches? Just the sysadmin? Anybody?
Somewhere in between? Different solutions are likely to be optimal given
different answers.
At 04:02 PM 4/9/99 -0400, Michael B. Trausch wrote [abridged]:
>It seems like, you would want a system that would do something like every
>24 hours, finger all users, save this stuff into a file, and then, when
>you want something, grep the file.
>On Fri, 9 Apr 1999, Justin Wilson wrote:
JW> When I finger Corpoarte it does not return anything. If I have a user
JW>with the username or Name Corporate, it will return these. what I am looking
JW>for is a way to "search" or finger the different things in the finger info.
JW>Things such as the .plan, .project or whatever. I want to be able to finger
JW>Corporate and have it come up with all the corporate users.
[rest deleted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
