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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090289
Title:
Commands with backslashes are making troubles
To manage notifications about this bug go to:
https://bugs.launchpad.net/libnih/+bug/1090289/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
