> > > On Sat, 2013-06-08 at 09:08 -0400, Jeff Layton wrote: > > > > cifs.upcall.c | 8 ++++++-- > > > > 1 file changed, 6 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/cifs.upcall.c b/cifs.upcall.c > > > > index 6c0b9de..5a6c7d7 100644 > > > > --- a/cifs.upcall.c > > > > +++ b/cifs.upcall.c > > > > @@ -805,13 +805,14 @@ lowercase_string(char *c) > > > > > > > > static void usage(void) > > > > { > > > > - fprintf(stderr, "Usage: %s [-k /path/to/krb5.conf] [-t] [-v] [-l] key_serial\n", prog); > > > > + fprintf(stderr, "Usage: %s [ -d /path/to/keytab] [-k /path/to/krb5.conf] [-t] [-v] [-l] key_serial\n", prog); > > > > } > > > > > > > > const struct option long_options[] = { > > > > {"krb5conf", 1, NULL, 'k'}, > > > > {"legacy-uid", 0, NULL, 'l'}, > > > > {"trust-dns", 0, NULL, 't'}, > > > > + {"dedicated-keytab", 1, NULL, 'd'}, > > > > {"version", 0, NULL, 'v'}, > > > > {NULL, 0, NULL, 0} > > > > }; > > > > @@ -839,11 +840,14 @@ int main(const int argc, char *const argv[]) > > > > > > > > openlog(prog, 0, LOG_DAEMON); > > > > > > > > - while ((c = getopt_long(argc, argv, "ck:ltv", long_options, NULL)) != -1) { > > > > + while ((c = getopt_long(argc, argv, "cd:k:ltv", long_options, NULL)) != -1) { > > > > switch (c) { > > > > case 'c': > > > > /* legacy option -- skip it */ > > > > break; > > > > + case 'd': > > > > + keytab_name = optarg; > > > > + break; > > > > case 't': > > > > try_dns++; > > > > break; > > > > -- > > > > 1.8.1.4 > > > > > > > > > > Hi > > > Brilliant. > > > I applied the patch, well, I edited cifs.upcall.c with the -'s and +'s > > > at least. I then, make clean, build and make install. I now have: > > > cifs.upcall > > > Usage: cifs.upcall [ -d /path/to/keytab] [-k /path/to/krb5.conf] [-t] > > > [-v] [-l] key_serial Hi Jeff Would there be any possibility of including this patch in a cifs-utils release? It's just that we're not allowed to use patched versions outside the lab. Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html