From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/docs user_manual.html
Date: 25 Jun 2007 19:27:24 -0000 [thread overview]
Message-ID: <20070625192724.30712.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Branch: RHEL5
Changes by: jparsons at sourceware.org 2007-06-25 19:27:24
Modified files:
luci/docs : user_manual.html
Log message:
fix for bz239327
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/docs/user_manual.html.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.7.2.3&r2=1.7.2.4
--- conga/luci/docs/user_manual.html 2007/01/15 21:43:15 1.7.2.3
+++ conga/luci/docs/user_manual.html 2007/06/25 19:27:24 1.7.2.4
@@ -40,7 +40,8 @@
can be started with the command "service luci start". The first time the
server is started, it is initialized by generating https SSL certificates
for that server and an initial password for the admin user is generated as a
- random value. The admin password can be set any time by running the
+ random value. The admin password can be set any time by first stopping
+ the luci service with 'service luci stop, and then running the
/usr/sbin/luci_admin application and specifying "password" on the command
line. luci_admin can be run before luci is started for the first time to set
up an initial password for the admin account. Other utilities available from
next reply other threads:[~2007-06-25 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 19:27 jparsons [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-15 21:43 [Cluster-devel] conga/luci/docs user_manual.html jparsons
2007-01-15 21:41 jparsons
2007-01-15 21:23 jparsons
2007-01-15 20:33 rmccabe
2007-01-15 20:26 rmccabe
2007-01-15 20:03 jparsons
2007-01-15 19:57 rmccabe
2007-01-15 19:46 jparsons
2007-01-15 16:00 jparsons
2006-10-10 18:31 rmccabe
2006-10-09 5:47 jparsons
2006-09-26 13:35 jparsons
2006-09-26 12:36 jparsons
2006-09-26 12:12 jparsons
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=20070625192724.30712.qmail@sourceware.org \
--to=jparsons@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).