Do not use /dev/stdout or stderr, running under sudo fails with permission errors. about cms-git-tools HOT 7 CLOSED

Another easy "work-around" is to use script(1):

exec script /dev/null

"script" is a command which captures (to a file, which is /dev/null in our case) anything you type and output, but more importantly, it has to reopen the stdin/out/err in order to capture them (and they are created with correct permissions).

Dmitrijus

from cms-git-tools.

Thanks for reporting this. Can you please specify why you were running git cms-addpkg via sudo / cron? In principle git-cms-* are for interactive usage and you are much better off using normal git commands if you need to do things non interactively. Of course if you have a patch for this it will not be rejected though.

from cms-git-tools.

In online dqm we run our stuff inside a special dqmdev/dqmpro user,
and we usually set up cmssw inside interactively via sudo bash.

Our code is changing quite often and the git tools are quite useful.
I won't make a patch (for now), running under "script" solves the problem.

As for cron - I do not use it, but I remember Antanas and several summer students complaining about this bug.

from cms-git-tools.

Partially addressed by #78 .

from cms-git-tools.

A new Issue was created by @dmitrijus Dmitrijus.

@davidlange6, @smuzaffar, @Dr15Jones can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here cms-sw/cmssw#13029

from cms-git-tools.

@dmitrijus is this still an issue ?

from cms-git-tools.

I did a quick check it and it seems to work fine.
Thanks.

from cms-git-tools.