THanks Sanel, will try and let you know the result. Regards Prabhakar
On Mon, Aug 23, 2021 at 2:21 PM Sanel Zukan <[email protected]> wrote: > Try with --silent=true or "-log drill.log" arguments. Or redirect nohup > to /dev/null, with "nohup drill-embedded > /dev/null 2>&1". > > Best, > Sanel > > Prabhakar Bhosaale <[email protected]> writes: > > Hi All, > > We are deploying drill in standalone mode on production and starting it > > with nohup. But with nohup it is generating a huge log file. So > > following are the questions. > > > > 1. Is it the correct way to start drill with nohup? If not then what is > the > > alternative to keep it running? > > 2. Are there any settings to reduce the logging in nohup. or change the > > location of the log file? Currently the log file is getting created under > > the bin folder. > > > > Thanks and regards > > Prabhakar >
