On Sat, May 2, 2009 at 5:47 PM, <[email protected]> wrote: > What's the specific problem with putting a password in a crontab or a shell > script that cron calls? Only folks with root access could see the > password. Besides, you've got to put the RT database password in plain > text in your RT_SiteConfig file, unless you are running without a password, > which is even worse...
good point. that answered my question > > > I haven't used the CLI, but if it's truly interactive, you'll need to write > an expect script. > > BTW, it appears you didn't catch my email with specific instructions for > creating a Logo file... I tried to follow. Is it possible to point to what I have done wrong based on my last repy to that email. Thanks for your help > > > > James Moseley > > > > Asif Iqbal <[email protected]> wrote: > > The rt cli from 2001 does not require a password to get the content of a > ticket. So running it as part of a cron is not a problem > > To get the content of a ticket with rt cli from rt-3.8.2 I need to run rt > show <ticket number>, but it requires a password. > So I need to run it interactively. Plus I am not comfortable to feed a > password in cronjob. > > How do I by pass the password prompt? Is there another user I can use > instead where I don't have to feed a password thru cronjob? > > > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
