| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The umask was set to zero in order to address the issue that mknod(2)'s
mode argument is modified by the process's umask. However, this umask
setting also affected auto-created parent directories of configuration
entries: their permissions were set to `drwxrwxrwx'. So, we now call
chmod(2) after mknod(2) instead of setting the umask to zero.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
|
|
| |
Make sure the "start_sequence" variable is initialized. This fixes a
traceback which occurred when a <Service> "sequence" has been specified
on Debian systems which use dependency-based booting.
|
|
|
|
|
|
|
|
|
| |
The "-f" option, which tells the client to configure from a file rather
than querying the server, cannot be combined with the "-l" option (nor
with the equivalent setting in the bcfg2.conf(5) file), as a decision
list won't be available. Instead of crashing (with a KeyError:
'decision_list'), the client will now ignore the "-l" option if the "-f"
option also is specified.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
If the file /etc/init.d/.legacy-bootordering exists, dependency-based
booting isn't used, even when running on Debian releases newer than
lenny.
|
| |
|
|
|
|
| |
Options.SERVER_PLUGINS.default
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
| |
The client now makes sure that an entry won't be reported as modified if
the Install() method which handled the entry returned False.
|
|
|
|
| |
cb8b988774c573bb8f6840aa60be0ced60323940
|
|
|
|
|
|
| |
Make the database_port configuration parameter optional (as documented
in doc/reports/dynamic.txt). The default port will now be used if the
database_port is not explicitly set.
|
|
|
|
|
| |
Fix the problem that modified entries weren't included in the client
statistics if their "important" attribute was set to "true".
|
|
|
|
|
| |
section.
(cherry picked from commit 54e70421bd1aea5bdd495cf48767b88cfe82b3b1)
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Instead of always creating DSA, RSA, and RSA1 key pairs when any of them
is missing, create only the key pair currently requested via Bcfg2.
That is, the abstract configuration entries now determine which key
types are generated (and therefore included in the ssh_known_hosts
files).
The rationale is that many sites don't use RSA1 keys anymore.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
| |
Ignored files (like Vim swap files) were being picked up by the File
Monitor and were causing tracebacks because they are invalid XML. Now
check for such ignored file patterns before doing any other
processing.
(cherry picked from commit c266631eb36e117bad0f297506dc301ee9cc0487)
|
|
|
|
|
|
|
| |
This fix is more complete than 8059a36 and also fixes issues relating to
the use of wildcards in Decisions.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| |
| |
| |
| |
| | |
toggle "[+]" to "[-]" and back on expanding/collapsing lists
make the whole header bar clickable
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From the ticket:
A floating, cert-authenticated client can be not recognized properly by
hostname if it resolves to an arbitrary name in reverse DNS.
Background: Metadata.resolve_client, called from @exposed Core's
methods, falls back to reverse DNS lookup for client's name, because the
name is not preserved thanks to bailing off early from
Metadata.AuthenticateConnection.
(This issue can be related to #936.)
This patch enables caching of client names for cert-based floating
clients.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|/ |
|
|
|
|
|
|
| |
Don't run 'post' Action entries if they are unlisted in whitelist mode.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
Previously, we wanted one second for the FileMonitor to notify us
about newly generated SSHkeys. Now, we wait up to ten seconds before
logging a warning and giving up.
(cherry picked from commit 204ddcddea55b1f8eed5f6dfe4dd2967bac5bad7)
|
|
|
|
|
|
|
|
|
| |
Previously, if we got a "changed" event for a path we weren't
monitoring, we would log a warning and ignore it. Now, we log the
warning, but treat it like a "created" event so we know about the
file/directory going forward. This situation shouldn't occur, but this
new logic will handle it a little better.
(cherry picked from commit 29701f299632ea343d7b58af4d3b7a143ced0078)
|
| |
|