Thanks for your replies, So in total it would be something like this: ExecStart=/bin/sh -c /opt/sge/bin/sge_qmaster |&grep -v '^RUE_' >&/dev/null ?
Cheers 2018-03-23 10:58 GMT+01:00 William Hay <w....@ucl.ac.uk>: > On Fri, Mar 23, 2018 at 09:36:29AM +0000, Mark Dixon wrote: > > Hi Jakub, > > > > That's right: if you need to cut down the logging, one option is to add > the > > redirection in the start script. > > > > You're looking for the line starting "sge_qmaster", and you might want to > > try adding a ">/dev/null" after it. You'll lose all syslog messages from > > sge_qmaster though (normally, most useful messages end up in > > $SGE_ROOT/$SGE_CELL/spool/qmaster/messages, but you might want to > remove the > > redirection if you ever find that sge_qmaster refuses to start). > > The qmaster man page says debug output goes to stderr not stdout so that > would probably need to be a ">&/dev/null" rather than a plain ">/dev/null" > > Assuming qmaster is launched from a shell script you might be able to add > a "|&grep -v '^RUE_'" > after the qmaster invocation to just get rid of these messages while > keeping others. > > There might be a few issues with that though if the script replaces itself > with the qmaster > via exec or similar in order to ensure the qmaster has the same pid as the > script systemd > launched. > > William > >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users