![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Bugger me I think it works; just ran an onbar backup of a couple of dbspaces as user informix and got no errors. I added the following entries to the ‘/opt/sudo/etc/sudoers/sudoers’file: User_Alias IMIX=informix,dba (at the end of the existing user aliases) And: IMIX ALL=(ALL) NOPASSWD:/opt/informix/bin/onbar IMIX ALL=(ALL) NOPASSWD:/opt/informix/bin/savegrp (In the “user privilege specification’ section) So it looks like the call to savegrp is covered. Thanks for your help, Clive, appreciated! |
#12
| |||
| |||
|
|
Ignoring the comedians sideshow - you're welcome And you PROBABLY don't need the sudoers entry for savegrp as it's being run by onbar that is 'already' root ....which also turns out correct, ta. |
#13
| |||
| |||
|
|
One more thing ((c) 2010). It is a TOTAL pain in that with ISM you have to be root to run the backup commands. The root user round here is under tighter security than a very nervous camel's backside in a very powerful sandstorm. They are really NOT happy about adding anything to root cron or 'at' or into their imprenetrable schedule, and database backups don't register much if at all on their 'things we want/need/have to do' radar. Is there any way at all of allowing the informix user to run the backup commands without ISM triggering the "07/27/10 10:15:41 savegrp: You are not authorized to run this command" error? It basically means that no bootstrap file can be created if user informix runs the backups (whether database ot logical log) Ta |
#14
| |||
| |||
|
|
informix should be able to run backups fine including savegrp. Run ism_show -admins and check that informxi@hostname is configure as an admin for the ISM server other use ism_add -admins informix@hostname |
![]() |
| Thread Tools | |
| Display Modes | |
| |