From: Neil Brown <neilb@suse.de>
To: "Kevin Coffman" <kwc@citi.umich.edu>
Cc: "Steinar H. Gunderson" <sgunderson@bigfoot.com>,
nfs@lists.sourceforge.net
Subject: Re: [PATCH] fix rpc.gssd -d
Date: Mon, 5 Feb 2007 09:53:59 +1100 [thread overview]
Message-ID: <17862.25607.109790.62992@notabene.brown> (raw)
In-Reply-To: message from Kevin Coffman on Thursday January 4
On Thursday January 4, kwc@citi.umich.edu wrote:
> Thanks Steinar. I'll get to this and the AM_MAINTAINER_MODE patch
> soon and resend them to Neil. (Your other recent patches are out of
> my arena.)
I've applied this patch as it is trivially correct.
Thanks.
NeilBrown
>
> K.C.
>
> On 1/4/07, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
> > Fix an off-by-one in the handling of the -d option to rpc.gssd; this makes
> > the option usable again (it would complain that the string was too long).
> > This patch is originally by Liam Bedford, and extracted from
> >
> > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/76409
> >
> > --- nfs-utils-1.0.10.orig/utils/gssd/gssd.c
> > +++ nfs-utils-1.0.10/utils/gssd/gssd.c
> > @@ -118,7 +118,7 @@ main(int argc, char *argv[])
> > break;
> > case 'd':
> > strncpy(ccachedir, optarg, sizeof(ccachedir));
> > - if (ccachedir[sizeof(ccachedir-1)] != '\0')
> > + if (ccachedir[sizeof(ccachedir)-1] != '\0')
> > errx(1, "ccachedir path name too long");
> > break;
> > default:
> >
> > /* Steinar */
> > --
> > Homepage: http://www.sesse.net/
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > NFS maillist - NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
> >
> >
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-02-04 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 19:46 [PATCH] fix rpc.gssd -d Steinar H. Gunderson
2007-01-04 20:54 ` Kevin Coffman
2007-01-04 23:51 ` Steinar H. Gunderson
2007-02-04 22:51 ` Neil Brown
2007-02-04 23:09 ` Neil Brown
2007-02-04 22:53 ` Neil Brown [this message]
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=17862.25607.109790.62992@notabene.brown \
--to=neilb@suse.de \
--cc=kwc@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
--cc=sgunderson@bigfoot.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.