-d fails to initiate daemon mode on Ubuntu Karmic
Bug #511815 reported by
Russel Winder
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar hookless email |
New
|
Undecided
|
Unassigned |
Bug Description
I used to have lots of daemons monitoring a bunch of branches. They get started with @reboot entries in cron tables. Since the upgrade to Karmic from Jaunty, -d fails to initiate daemon mode so the daemons are not running.
Executing the command line from the cron table manually shows the failure is int he hookless email program and not cron.
To post a comment you must log in.
I found this in ~/.bzr_ hookless_ email.tracebook :
Traceback (most recent call last): Checkouts/ Bazaar/ BazaarHooklessE mail/bzr_ hookless_ email.py" , line 393, in <module> Checkouts/ Bazaar/ BazaarHooklessE mail/bzr_ hookless_ email.py" , line 105, in main IN_CREATE | EventsCodes. IN_MODIFY | EventsCodes. IN_MOVED_ TO
File "/home/
main()
File "/home/
mask = EventsCodes.
AttributeError: type object 'EventsCodes' has no attribute 'IN_CREATE'
So I looked in bzr_hookless_ email.py and it is assumed that the OP_FLAGS can all be accesed directly. The source code of pyinotify.py seems to indicate that this should work. However:
|> python -c "import pyinotify ; print pyinotify. EventsCodes. IN_MODIFY"
Traceback (most recent call last):
File "<string>", line 1, in <module>
AttributeError: type object 'EventsCodes' has no attribute 'IN_MODIFY'
So it seems that this way of accessing things is not longer working in Karmic whereas it worked fine in Jaunty.