summaryrefslogtreecommitdiff
path: root/source3
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2002-01-09 08:17:12 +0000
committerMartin Pool <mbp@samba.org>2002-01-09 08:17:12 +0000
commita56f0e93ea775ede87de478f9b09de2daa72ca27 (patch)
treec4bcf064f200c1ae7d5c26b7489e330cd50923eb /source3
parentf5bc0e92a66b418b2bd8f3669a9642b4d46bc8d1 (diff)
downloadsamba-a56f0e93ea775ede87de478f9b09de2daa72ca27.tar.gz
samba-a56f0e93ea775ede87de478f9b09de2daa72ca27.tar.bz2
samba-a56f0e93ea775ede87de478f9b09de2daa72ca27.zip
FIXME: At the moment, if the user should happen to give the options
ahead of the service name (in standard Unix fashion) then smbclient just spits out the usage message with no explanation of what in particular was wrong. Is there any reason we can't just parse out the service name and password after running getopt?? (This used to be commit 5f6feb55d7e7566549141ebb1786b6f2f9f2645b)
Diffstat (limited to 'source3')
-rw-r--r--source3/client/client.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/source3/client/client.c b/source3/client/client.c
index 33ce7e30f7..f5f27474d9 100644
--- a/source3/client/client.c
+++ b/source3/client/client.c
@@ -2499,7 +2499,13 @@ static int do_message_op(void)
usage(pname);
exit(1);
}
-
+
+ /* FIXME: At the moment, if the user should happen to give the
+ * options ahead of the service name (in standard Unix
+ * fashion) then smbclient just spits out the usage message
+ * with no explanation of what in particular was wrong. Is
+ * there any reason we can't just parse out the service name
+ * and password after running getopt?? -- mbp */
if (*argv[1] != '-') {
pstrcpy(service,argv[1]);
/* Convert any '/' characters in the service name to '\' characters */