|
|
| Subject: | Zenoss 5 - modifying Zenoss core code - what containers and how to persist? |
| Author: | Jane Curry |
| Posted: | 2016-03-17 13:37 |
I currently have Zenoss 5.0.7. There is a bug with $ZENHOME/Products/ZenModel/actions.py that looks like it has a 2-line fix - https://github.com/zenoss/zenoss-prodbin/commit/1cb79b7724e6c554ee5ae4e30bb1b3127feb266c .
What is the correct procedure to modify actions.py
Just accessing the Zope container with:
serviced service attach zope su zenoss -l
and then copying and changing the file, doesn't persist.
Thanks,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | I feel strange asking the |
| Author: | [Not Specified] |
| Posted: | 2016-03-17 14:23 |
I feel strange asking the question to someone who's practically written half the code *in* Zenoss - kind of like an art student asking Picasso -but the snapshot that serviced generates *was* committed afterwards with a "serviced snapshot commit"
| Subject: | What I have found to work for |
| Author: | [Not Specified] |
| Posted: | 2016-03-26 20:44 |
What I have found to work for any container Jane is:
serviced service shell -s
serviced snapshot commit
Manuel
| < |
Previous Can't POST data from Zenoss to other server |
Next Zenoss + webSSO (using SSSD or freeIPA or Kerberos?) |
> |