Displaying 5 results from an estimated 5 matches for "unexcit".
Did you mean:
onexit
2011 Mar 01
1
1.0.15 -> 2.x upgrade for mass hosting environment
Hi all,
We're looking at upgrading our current mail platform from 1.0.15 to
2.x to take advantage of the new director functionality.
Our main concern is the number of mailboxes involved (circa. 300K) and
the rebuilding of the index files, especially as it seems that once
you've upgraded, rolling back requires the deletion and recreation of
all indices.
Has anyone worked on an
2025 May 14
2
UPS configuration issue?
...31, 2023: NUT 2.8.1 released" - so at the time
they had no other NUT to put into the baseline than the newest (at the
time) 2.8.0. And it's great they made the effort and did not ship 2.7.4
again :D
As I said before, "Stable" may mean "stale", but primarily it is
"unexciting" - no cutting edge features, but also no surprises and bugs for
you being the first to discover after a couple of years of use and interim
minor updates. It is not only about lack of volunteer time (and as the
adage goes, staying on the outside and donating a bit sometimes can not
help the...
2013 Nov 27
8
noop = true and what for test?
Hi,
When I put
noop = true
in /etc/puppet/puppet.conf
on the node in question, I observe no changes. Great. Good
But also, I see because of
report = true
absolutely zero information in the yaml regarding what would have
been changed.
Is there an equivalent to the above for "test = true" or must I alter
the rc file to include --test ?
Thanks ahead Puppet wizards!!!
--
You
2025 May 14
1
UPS configuration issue?
On 5/13/25 21:05, Sam Varshavchik wrote:
> gene heskett via Nut-upsuser writes:
>
>> However debians legendary slowness to update things does test my
>> patience at times. The fact that bookworms default nut is 2.8.0 is an
>> example.
>
> That sounds familiar. Debian's been shipping very old versions of my
> packages, which was ?irritating. I am not being
2016 Dec 14
0
Cannot get plaintext+pam auth to work on 4.2.10
...yes
encrypt passwords = no
lanman auth = yes
ntlm auth = no
server max protocol = LANMAN2
client lanman auth = yes
client plaintext auth = yes
client ntlmv2 auth = no
; the above seem relevant, see below for dump of full config
[data]
path = /srv
read only = no
3) /etc/pam.d/samba is at unexciting default:
@include common-auth
@include common-account
@include common-session-noninteractive
4) and yet:
porridge at piec:~$ smbclient -U smbtest //localhost/data asdasd
session setup failed: NT_STATUS_ACCESS_DENIED
porridge at piec:~$
It seems that the password is being sent as plaintext,...