[Bug 1090289] Re: Commands with backslashes are making troubles

[James Hunt]

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

** Changed in: upstart (Ubuntu)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Also affects: upstart
   Importance: Undecided
       Status: New

** Changed in: upstart
       Status: New => Confirmed

** Changed in: upstart
   Importance: Undecided => Medium

** Changed in: upstart
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Also affects: libnih
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1090289

Title:
  Commands with backslashes are making troubles

Status in NIH Utility Library:
  New
Status in Upstart:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libnih/+bug/1090289/+subscriptions