Submitted by SteveHeinsch on Tue, 09/24/2013 - 11:40Comment #12
I am actually experiencing this exact same thing as well. I've deleted the cron job and recreated it from scratch with no copy/pasting. Same issue. Each time I save it adds a new trailing "\" after the cron job command.
/usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com
becomes
/usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com \
and then resaving adds an extra space and another slash like
/usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com \ \
Another similar issue is happening with the description. Any place there is a space it appears to escape it, and then reescapes upon each save adding new slashes.
So if I enter "Cron test" for the description and save I get "Cron\ test". If I save again without doing anything, I get "Cron\\ test".
Comments
Submitted by JamieCameron on Wed, 01/27/2010 - 12:01 Comment #1
Could you give us an example of the exact command this is happening for?
the command is:
php /home/mailout/public_html/_site/send_messages.php
Submitted by JamieCameron on Thu, 01/28/2010 - 11:41 Comment #3
Ok, that looks fine to me ..
What does it get transformed to after saving?
Also, did you enter anything in the "Input to command" box?
transformed into:
php /home/mailout/public_html/_site/send_messages.php \
Nothing entered into "Input to command" box.
If, for example I were to save it again you get:
php /home/mailout/public_html/_site/send_messages.php \ \
It looks like an escaping issue as if I put two words into the "description" box, and then save the job, I get Cron\ job
Submitted by JamieCameron on Fri, 01/29/2010 - 12:39 Comment #5
You are right, this looks like an escaping issue ..
Which browser are you using there?
I'm using Firefox 3.6 on Windows Vista.
Submitted by JamieCameron on Mon, 02/01/2010 - 13:05 Comment #7
Wierd, I just can't re-produce this.
Does this happen for all cron jobs, or just that one?
This is happening on just this one cron job.
when i recreate the cron job i cant reproduce it.
Submitted by JamieCameron on Fri, 02/05/2010 - 11:49 Comment #9
All I can guess is that there is a hidden character in the cron job command, like a null byte. I'd suggest just deleting and re-creating it.
deleted the job and re-added. no trailing \
Submitted by JamieCameron on Tue, 02/09/2010 - 11:30 Comment #11
Ok .. I think we can close this bug then.
Submitted by SteveHeinsch on Tue, 09/24/2013 - 11:40 Comment #12
I am actually experiencing this exact same thing as well. I've deleted the cron job and recreated it from scratch with no copy/pasting. Same issue. Each time I save it adds a new trailing "\" after the cron job command. /usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com becomes /usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com \ and then resaving adds an extra space and another slash like /usr/bin/php5 -q /home/xxx/public_html/cron_bs.php --run=/cron/test --server=www.xxx.com \ \
Another similar issue is happening with the description. Any place there is a space it appears to escape it, and then reescapes upon each save adding new slashes.
So if I enter "Cron test" for the description and save I get "Cron\ test". If I save again without doing anything, I get "Cron\\ test".
VM 4.01 pro
Submitted by SteveHeinsch on Tue, 09/24/2013 - 11:56 Comment #13
Tried in Firefox and also Chrome, same results creating the job from scratch manually typing it in
Submitted by JamieCameron on Tue, 09/24/2013 - 14:22 Comment #14
For those who are seeing this issue - which Linux distribution and version are you running?
Submitted by SteveHeinsch on Tue, 09/24/2013 - 14:35 Comment #15
Ubuntu 12.04LTS
Submitted by JamieCameron on Tue, 09/24/2013 - 14:48 Comment #16
Actually, I see the bug here now - it only triggers for cron jobs that have a date range set.
This will be fixed in the next webmin release.
Submitted by Issues on Tue, 10/08/2013 - 16:42 Comment #17
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Tue, 10/08/2013 - 17:51 Comment #18
Automatically closed -- issue fixed for 2 weeks with no activity.