Issue 322 in redis: Can't configure server parameters from command line (with patch)

21 views
Skip to first unread message

re...@googlecode.com

unread,
Sep 4, 2010, 3:06:16 PM9/4/10
to redi...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 322 by pc.reader00: Can't configure server parameters from
command line (with patch)
http://code.google.com/p/redis/issues/detail?id=322

What steps will reproduce the problem?

redis-server currently reads configuration directives from a config file
specified on the command line. It would be convenient to be able to be able
to configure the server from the command line using standard --option=value
syntax however this is not currently supported (a note in the config.c file
suggests that there is an intent to change this at some point)

Note: it is possible to configure options using a "here-doc"

What is the expected output? What do you see instead?

./redis-server --port=9999 (etc)

Sets appropriate configutation options

What version of the product are you using? On what operating system?

git head - Mac OS-X
Redis server version 2.1.4 (556bdfba:1)

Please provide any additional information below.

A patch which enables '--option=value' support is attached below. This is
actually pretty simple - it moves the current option parsing logic into a
separate function which can be called either by the config file parser and
adds a simple cli argument parser which extracts configuration options and
dynamically passes them to the option parser - this ensures that we don't
have to define the logic twice or hardcode the options into the cli parser
(as would be needed by getopt-long)

Attachments:
cli-options.diff 19.9 KB

re...@googlecode.com

unread,
Sep 6, 2010, 4:05:52 AM9/6/10
to redi...@googlegroups.com
Updates:
Status: WontFix

Comment #1 on issue 322 by antirez: Can't configure server parameters from

Hello, this is the Redis way of doing it:

echo "port 8888" | ./redis-server -

Cheers,
Salvatore

re...@googlecode.com

unread,
Feb 5, 2015, 7:47:43 PM2/5/15
to redi...@googlegroups.com

Comment #2 on issue 322 by georgelo...@gmail.com: Can't configure server
parameters from command line (with patch)
https://code.google.com/p/redis/issues/detail?id=322

Yeah, 'cause that totally fucking works for the pidfile option or similar.

Not supporting command line configuration is pants-on-head retarded even
for the NoSQL folks.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

re...@googlecode.com

unread,
Feb 5, 2015, 9:04:14 PM2/5/15
to redi...@googlegroups.com

Comment #3 on issue 322 by josiah.c...@gmail.com: Can't configure server
parameters from command line (with patch)
https://code.google.com/p/redis/issues/detail?id=322

You know what else is pants-on-head retarded?

Commenting on an issue 4+ years after it was closed thinking it will revive
the issue, 3+ years after development and issue tracking was moved to
Github, and 3+ years after the project added command-line argument parsing:
https://github.com/antirez/redis/commit/67c6f0f6 .

Troll harder and better next time, this was too easy.
Reply all
Reply to author
Forward
0 new messages