Commands with backslashes are making troubles

Bug #1090289 reported by Removed by request
6
Affects Status Importance Assigned to Milestone
libnih
New
Undecided
Unassigned
upstart
Confirmed
Medium
James Hunt
upstart (Ubuntu)
Confirmed
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.

Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.