Thanks for clearing that up. I was pretty sure there was no problem at all in
using logrotate, and I know that restarting slurmctld does not ordinarily lose
jobs.
--
____
|| \\UTGERS, |---------------------------*O*---------------------------
||_// the State | Ryan Novosielski - novos...@rutgers.edu
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
|| \\ of NJ | Office of Advanced Research Computing - MSB C630, Newark
`'
> On Oct 11, 2016, at 06:19, Philippe <philippe.ra...@gmail.com> wrote:
>
> Hello all,
> sorry for this long delay since my first post.
> Thanks for all the answers, it helped me to make some tests, and after not so
> long, I realize I use a personnal script to launch the daemons, and I was
> still using my "debug" start line, which contains the startclean argument ...
> So it's all my fault, Slurm did his job to startclean when the logrotate
> triggered it.
>
> Sorry for that !
>
> On Thu, Sep 29, 2016 at 2:05 PM, Janne Blomqvist <janne.blomqv...@aalto.fi>
> wrote:
> On 2016-09-27 10:39, Philippe wrote:
> > If I can't use logrotate, what must I use ?
>
> You can log via syslog, and let your syslog daemon handle the rotation
> (and rate limiting, disk full, logging to a central log host and all the
> other nice things that syslog can do for you).
>
>
> --
> Janne Blomqvist, D.Sc. (Tech.), Scientific Computing Specialist
> Aalto University School of Science, PHYS & NBE
> +358503841576 || janne.blomqv...@aalto.fi
>
>
