incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Smythe <>
Subject Re: duplicate lines in futon config screen
Date Wed, 01 Feb 2012 03:47:53 GMT
Yeah, it was just an idea...

You might have to quote the command to run and add some flags to follow

you might also be able to look at ps output to find the actual binary and
arguments that that startup script (I'm guessing) its executing, and run
that directly.

I opted for the strace route because I figured that the process wouldn't
keep a file handle open very long, so using lsof on the running process
might not show the config files because most likely the process closes the
file handle after reading the config out of it...

Just trying to throw out some ideas for you.

Some other things I would try...

- delete the lines instead of commenting them
- delete the other config file, or rename it
- look around for hidden files with ls -la (if I remember right, couch uses
a lot if hidden files and directories)

Really though, most sure fire way is going to be to get a good strace on
the process and grep out every file open..

If you find that only the config files you know about are read.... Then its
possibly a bug...

Best of luck
On Jan 31, 2012 8:38 PM, "Mark Hahn" <> wrote:

> >   I bet you could strace the couch process when it starts and look at all
> the fread calls to find out
> what files its reading.
> I had never heard of strace.  It looks great. Unfortunately this is what I
> got when I added strace to the beginning of a cmd line that worked.  I
> assume I'm not using it correctly.
> $ strace /root/build-couchdb/build/bin/couchdb start
> execve("/root/build-couchdb/build/bin/couchdb",
> ["/root/build-couchdb/build/bin/co"..., "start"], [/* 31 vars */]) = -1
> ENOEXEC (Exec format error)
> dup(2)                                  = 3
> fcntl64(3, F_GETFL)                     = 0x8002 (flags O_RDWR|O_LARGEFILE)
> fstat64(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
> 0xb7741000
> _llseek(3, 0, 0xbfd297f4, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
> write(3, "strace: exec: Exec format error\n", 32strace: exec: Exec format
> error
> ) = 32
> close(3)                                = 0
> munmap(0xb7741000, 4096)                = 0
> exit_group(1)                           = ?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message