Bug with mogstored command line arguments

31 views
Skip to first unread message

Jon Skarpeteig

unread,
May 6, 2013, 8:30:45 AM5/6/13
to mogile
mogstored --httplisten 127.0.0.20:7500 --mgmtlisten 127.0.0.20:7501 --
docroot /var/mogdata/127.0.0.20

Running.
ERROR: Need to be root to increase max connections.
ERROR: Can't start service 'mogstored' on 127.0.1.5:7001: Error
creating listening socket: IO::Socket::INET: Address already in use
Invalid configuration. (shouldn't happen?) Stopping.

Why doesn't command line parameters take precedence? The
127.0.0.5:7001 is defined in /etc/mogilefs/mogstored.conf which I
don't expect to overwrite command line options. Renaming
mogstored.conf to foo.conf solves the problem.

Eric Wong

unread,
May 6, 2013, 1:13:05 PM5/6/13
to mog...@googlegroups.com
2.65 and later added a --skipconfig switch to bypass the default
config file.

But command-line arguments should probably bypass what's in the
_default_ config file... Currently mogstored doesn't make a distinction
when loading default vs -c (user-specified) config files. Perhaps it
should?

dormando

unread,
Dec 16, 2014, 2:13:32 AM12/16/14
to mog...@googlegroups.com
Could it? Any interest in patching? Seems pretty wrong.
Reply all
Reply to author
Forward
0 new messages