cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/utils luci_admin
Date: 10 Aug 2007 18:36:31 -0000	[thread overview]
Message-ID: <20070810183631.27181.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	conga
Changes by:	rmccabe at sourceware.org	2007-08-10 18:36:31

Modified files:
	luci/utils     : luci_admin 

Log message:
	- backup returns -1, not 0 on failure.
	- do not warn about not being about to chown/chmod nonexistent backups

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/utils/luci_admin.diff?cvsroot=cluster&r1=1.54&r2=1.55

--- conga/luci/utils/luci_admin	2007/08/07 20:22:54	1.54
+++ conga/luci/utils/luci_admin	2007/08/10 18:36:31	1.55
@@ -161,12 +161,17 @@
 		os.chmod(LUCI_DB_PATH, 0600)
 		for ext in [ '.tmp', '.old', '.index', '.lock' ]:
 			cur_path = '%s%s' % (LUCI_DB_PATH, ext)
+
 			try:
 				os.chown(cur_path, uid, gid)
 				os.chmod(cur_path, 0600)
+			except OSError, eieio:
+				if eieio[0] != 2:
+					sys.stderr.write('Unable to change ownership of "%s" back to user "%s": %s\n' \
+						% (cur_path, LUCI_USER, str(eieio)))
 			except Exception, ei:
-				sys.stderr.write('Unable to change ownership of "%s" to user "%s": %s\n' \
-					% (cur_path, LUCI_USER, str(ei)))
+				sys.stderr.write('Unable to change ownership of "%s" to user "%s": %s %r\n' \
+					% (cur_path, LUCI_USER, str(ei), ei))
 	except Exception, e:
 		sys.stderr.write('Unable to change ownership of the Luci database "%s" back to user "%s": %s\n' \
 			% (LUCI_DB_PATH, LUCI_USER, str(e)))
@@ -1140,7 +1145,7 @@
 
 	doc = luci_backup(argv[2:])
 	restore_luci_db_fsattr()
-	if not doc:
+	if doc == -1:
 		sys.stderr.write('The Luci backup failed. Exiting.\n')
 		sys.exit(1)
 



             reply	other threads:[~2007-08-10 18:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 18:36 rmccabe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-25 20:14 [Cluster-devel] conga/luci/utils luci_admin rmccabe
2007-09-19  5:17 rmccabe
2007-08-10 18:33 rmccabe
2007-08-10 18:32 rmccabe
2007-08-07 20:22 rmccabe
2006-10-13  6:56 kupcevic
2006-08-18 18:03 rmccabe
2006-08-04 19:19 rmccabe
2006-08-04 18:37 rmccabe
2006-08-03 22:58 kupcevic
2006-08-03 21:19 rmccabe
2006-08-03 21:11 rmccabe
2006-08-03 16:32 rmccabe
2006-08-03 15:55 rmccabe
2006-08-03 12:26 rmccabe
2006-08-03  3:58 rmccabe
2006-08-03  3:30 rmccabe
2006-08-02 23:29 rmccabe
2006-08-02 20:52 rmccabe
2006-08-02 20:45 rmccabe
2006-07-26  1:17 rmccabe
2006-07-25 22:36 rmccabe
2006-07-11 18:46 rmccabe
2006-07-11 14:51 rmccabe
2006-06-29 18:04 rmccabe
2006-06-29 17:51 rmccabe
2006-06-27 19:50 rmccabe
2006-06-27 19:40 rmccabe
2006-06-27 18:19 rmccabe
2006-06-26 22:30 rmccabe
2006-06-26 20:01 rmccabe
2006-06-21 23:06 rmccabe
2006-06-21 17:41 rmccabe
2006-06-21 17:06 rmccabe
2006-06-18 15:02 rmccabe
2006-06-18 12:50 rmccabe
2006-06-18  3:26 rmccabe
2006-06-16 23:19 rmccabe
2006-06-16 19:35 rmccabe
2006-06-16 18:17 rmccabe
2006-06-16 17:44 rmccabe
2006-06-16  5:35 rmccabe
2006-06-13 18:42 rmccabe
2006-06-13 17:36 rmccabe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070810183631.27181.qmail@sourceware.org \
    --to=rmccabe@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).