git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git daemon --access-hook problem

From
ESEugene Sajine <euguess@gmail.com>
Date
Jun 3, 2013, 18:02 UTC
Message-ID
<CAPZPVFYdeuusW3=iBTBC+iPuOeAekvtMx6d_dozB9tsDCg3C8Q@mail.gmail.com>
In-Reply-To
<CALWbr2ypPCoftVLfP9uKeKStg3TWwLDchkUaL1d9s9O3kcuPwA@mail.gmail.com>
> - Your log file might not be located where you expect, you should use
> absolute path to dump text

You were right! The problem was with the script itself - the log file not being specified with absolute path! Stupid me!

...
> - The documentation says you can print one line before a failure, also
> try this to show the cwd

Would you be able to advise how this should be done? I don't get the error message (i mean the output of pwd) if i do this:

echo `pwd` exit 1

What should it be?

Thanks! Eugene

>
> Hope that helps,
> Antoine,
Previous: Antoine PelisseNext: Antoine Pelisse
Message 4 of 6 in “git daemon --access-hook problem”
  1. Eugene SajineMay 31, 2013
  2. Eugene SajineJun 3, 2013
  3. Antoine PelisseJun 3, 2013
  4. Eugene SajineJun 3, 2013
  5. Antoine PelisseJun 3, 2013
  6. Eugene SajineJun 3, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.