Just to clarify. Am I right that if 'crontab -l' returns empty list and there is no ~/...DATA.crontab in my home directory it means that my cron list has been lost completely?
Best regards, Artem. ________________________ Dr. Artem Korzhimanov Research Scientist Institute of Applied Physics of the Russian Academy of Sciences 46 Ulyanov st., Nizhny Novgorod, Russia Email: [email protected] 2014-05-01 13:37 GMT+04:00 Petr Bena <[email protected]>: > I don't think so. > > There is a number of cases where this is not relevant, I don't know > who added that into crontab, but I am pretty sure that nobody from > toolsadmin team is going to remove any line from it as long as it's > sane (for example some simple check that just submit some kind of > e-mail, tail some log file etc, doesn't need to be run as a job, since > the job itself is less resource expensive than submitting it to SGEN). > > So I think you can ignore this in your case. The note should be reworded > though. > > On Thu, May 1, 2014 at 11:34 AM, Danmichaelo > <[email protected]> wrote: > > Apologies accepted! But when crontab-ing now, I noted the comment: > > > > "Any command specified here will be modified to be invoked through jsub > > unless it is one of the two" [jsub or jstart] > > > > Does that mean I should move away from calling qsub directly? If so, > there > > should be a note about that here: > > > > > https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/Help#What_is_the_grid_engine.3F > > > > > > Dan Michael > > > > > > > > On 1 May 2014 02:31, Marc A. Pelletier <[email protected]> wrote: > >> > >> Hello all. > >> > >> Due to a (really) stupid mistake on my part, I have managed to > >> completely lose the crontab of any tool which had automatic changes > >> applied to it (the process which was supposed to make a backup before > >> any changes failed). This affects approximately 50 tools. > >> > >> Please accept my most sincere apologies for the work and lost data this > >> might cause. > >> > >> That said, if your tool existed before the migration to the new > >> datacenter, you probably still have the backup dating from that time in > >> your tool's home under the name ~/...DATA.crontab > >> > >> On the other hand, most tools' crontabs /were/ correctly moved to the > >> new system. There is a '/usr/local/bin/crontab' symlink now pointing to > >> xcrontab -- you should get that one by default unless you have changed > >> your default path. > >> > >> If you get a message along the lines of: > >> > >> You (user) are not allowed to use this program (/usr/bin/crontab) > >> > >> then you are accidentally hitting the wrong one; check your path or > type: > >> > >> hash -r > >> > >> To force your shell to revisit it. > >> > >> Again, please accept my apologies for the disruption. > >> > >> -- Marc > >> > >> _______________________________________________ > >> Labs-l mailing list > >> [email protected] > >> https://lists.wikimedia.org/mailman/listinfo/labs-l > > > > _______________________________________________ > > Labs-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/labs-l > > > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
