Nope. Like we said, we aren't making any guarantees about that.
Put a `mkdir -p` in your scripting :)
On 6/26/17 4:52 PM, Srikanth Viswanathan wrote:
Thanks, Josh and Mike.
This isn't causing any issues per se. We wanted to `chmod` the dir to be
publicly readable (for log aggregation), so there were questions around
where exactly to put the `chmod` call. I was then surprised to find that
the directory already existed. Do you recommend we rely on the directory
already existing after the distribution is untarred?
Thanks,
Srikanth
On Mon, Jun 26, 2017 at 4:50 PM, Michael Wall <[email protected]
<mailto:[email protected]>> wrote:
Srikanth,
Like Josh said, I don't think we make that guarantee. But it is
part of the maven assembly
(https://github.com/apache/accumulo/blob/rel/1.8.1/assemble/src/main/assemblies/component.xml#L91
<https://github.com/apache/accumulo/blob/rel/1.8.1/assemble/src/main/assemblies/component.xml#L91>)
so I would expect the directory to continue to be there. Is that
causing you issues?
On Mon, Jun 26, 2017 at 4:46 PM Josh Elser <[email protected]
<mailto:[email protected]>> wrote:
Srikanth,
I just checked 1.7.3 and 1.8.0, both of which have the logs/
directory
included in the bin-tarball. It isn't a change in packaging --
it's been
like this for some time.
I don't expect that we would provide any guarantees about the
presence
of this directory (but I don't know why we would chose to omit
it, either).
- Josh
On 6/26/17 4:27 PM, Srikanth Viswanathan wrote:
> Hi all,
>
> Kind of a silly question, but I noticed the `logs/` directory
being
> packaged with the accumulo binary release. Do you mean to
package this
> and do you guarantee this will be packaged in future releases?
>
> $ tar -tvf accumulo-1.8.1-bin.tar.gz |grep logs
> drwx------ mjwall/mjwall 0 2017-02-10 12:50
accumulo-1.8.1/logs/
>
>
> Thanks,
> Srikanth
