Commands with backslashes are making troubles

Reported by Sworddragon on 2012-12-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libnih
Undecided
Unassigned
upstart
Medium
James Hunt
upstart (Ubuntu)
Medium
James Hunt

Bug Description

I'm using Ubuntu 13.04 dev with upstart 1.6.1-1ubuntu1. For example an upstart script with this command isn't executed correctly:

exec find / ! -size 0 -regex '.*\.sqlite3?$' -type f -exec sqlite3 {} VACUUM \;

Copying the line into a terminal is working fine. A workaround to get this command working with upstart is to use the script tags around the command.

James Hunt (jamesodhunt) wrote :

Thanks for reporting. This looks like a subtle parsing issue.

A work-around is to put the entire command within a script stanza like this:

script
exec find / ! -size 0 -regex '.*\.sqlite3?$' -type f -exec sqlite3 {} VACUUM \;
end script

Changed in upstart (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → James Hunt (jamesodhunt)
Changed in upstart:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → James Hunt (jamesodhunt)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers