On Sun, 07 Jan 2007 03:23:59 +0100 Roland Mainz wrote:
> Glenn Fowler wrote:
> >
> > On Fri, 05 Jan 2007 09:19:25 +0100 Roland Mainz wrote:
> [snip]
> > note that the .paths file can also direct the shell to search for ksh
> > functions on path via
> > FPATH=../fun
> > so that just before
Mike Gerdts wrote:
>
> On 11/6/06, Darren J Moffat wrote:
[snip]
> I am not at all opposed to this proposal, I just suspect that a
> standard /tmp cleaner utility would have more impact. That is, do for
> /tmp cleaning what logadm has done for log rotation.
Erm... I am STRONGLY opposed to somet
Darren J Moffat wrote:
> Joerg Schilling wrote:
> > "Peter Tribble" wrote:
> >
> >> I regard this as unsafe and undesirable *as a default*. It clutters up
> >> /tmp with unnecessary directories, wastes memory and involves
> >> extra code at login. I have no problem with administrators or
> >> user
Henk Langeveld wrote:
> Roland Mainz wrote:
> > Is there any default location for loadable shell functions used by
> > ksh/bash/zsh/etc. ? AFAIK these shells all support loadable functions
> > (more or less) but do not seem to provide a "default" location similar
> > to /usr/include/ (for system he
Darren J Moffat wrote:
> Roland Mainz wrote:
> > Is there a nameservice-independent way to obtain the values for
> > "user_attr" and "publickey" from a shell script (if not I would propose
> > to add a extension to "getent") ?
>
> publickey no there isn't.
>
> For user_attr it depends which value
did my response to this yesterday drop on the floor?
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
On Sat, 06 Jan 2007 06:25:13 +0100 Roland Mainz wrote:
> Henk Langeveld wrote:
> > Roland Mainz wrote:
> > > Is there any default location for loadable shell functions used by
> > > ksh/bash
