From: Peter Stephenson <pws@hydra.ifh.de>
To: Matt Chidambaram <mc@prismtech.co.uk>
Cc: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: problems with $WATCH / $WATCHFMT
Date: Mon, 04 Dec 1995 18:12:27 +0100 [thread overview]
Message-ID: <9512041712.AA23824@hydra.ifh.de> (raw)
In-Reply-To: "mc@prismtech.co.uk"'s message of "Mon, 04 Dec 1995 15:01:00 MET." <Pine.OSF.3.91.951204143311.561C-100000@alpha3.prismtech.co.uk>
mc@prismtech.co.uk wrote:
> in those xterms that i dont work in very often - nothing happens until i
> press return every so often (ie every couple of hours); in these xterms -
> when i get the very similar login/out information as the other xterms -
> its great - except for the fact that the login/out times are effectively
> (plus/minus a minute) the time of day when i pressed return in that
> xterm/shell on that machine.
A problem is that after someone's logged out, they're not in utmp any
more, so the real logout time is impossible to get. The login time
should be OK, however ---- assuming the user is still logged on ---
otherwise it's a bug.
> is there any way of getting these login/out pieces of information to
> auto-interrupt my shell - without me having to press return before it
> displays the information? - say by setting an environemnt variable.
That's hard: you'd actually have to get the shell itself to wake up
and check every now and then. You might be best doing it some other
way, like a script running in the background.
> after reading the FAQ and doing as it says about copying ypclnt.h and
> altering the yp_all() signature's third parameter; i still get errors
> concerning the zle_tricky.c call to yp_all();
>
> i eventually altered the call from within zle_tricky.c ....
> from:
> yp_all(domain, PASSWD_MAP, &cb);
> to:
> yp_all(domain, PASSWD_MAP, cb);
That won't do: it definitely has to be &cb. The problems will start
when you try completing user names. It sounds like your problem is
with including the right version of ypclnt.h. Maybe I didn't put all
the instructions in the FAQ. At worst, change the #include for
ypclnt.h to
#include "my_ypclnt.h"
where my_ypclnt.h is the local modified copy of the header with the
corrected prototype.
--
Peter Stephenson <pws@ifh.de> Tel: +49 33762 77366
WWW: http://www.ifh.de/~pws/ Fax: +49 33762 77330
Deutches Electronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, 15735 Zeuthen, Germany.
next prev parent reply other threads:[~1995-12-04 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9505180204.AA00391@redwood.skiles.gatech.edu>
1995-05-18 16:30 ` new zsh mailing list up and running Mark Borges
1995-05-18 21:52 ` Richard Coleman
1995-05-19 5:44 ` procmail recipes Geoff Wing
1995-05-20 16:49 ` Deliver script (was Re: procmail) Chip Salzenberg
1995-12-04 15:01 ` problems with $WATCH / $WATCHFMT Matt Chidambaram
1995-12-04 16:53 ` Zoltan Hidvegi
1995-12-04 17:12 ` Peter Stephenson [this message]
1995-05-19 7:07 ` new zsh mailing list up and running Samuel Tardieu
1995-05-19 9:51 ` Martin Hamilton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9512041712.AA23824@hydra.ifh.de \
--to=pws@hydra.ifh.de \
--cc=mc@prismtech.co.uk \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).