similar to: [Bug 11668] New: incorrect/inconsistent behavior when --backup-dir is on a full filesystem

I believe I have encountered a nasty bug with rsync 2.6.6 "--delete-excluded" option. When this is enabled, rsync''s operation appears to break entirely. I have a script that I''ve been using for a few years. The script hasn''t changed in the last year or so. Recently I upgraded from SuSE 9.3 to SUSE 10.0 which means that I went from rsync 2.6.3 (+ patches,

Hi, Would it be possible to make this list accessible from gmane? www.gmane.org. Regards, -- Ugo Bellavance (ugob@lubik.ca) Consultant en Sécurité Informatique Lubik Inc. Site Web: http://www.lubik.ca # Tél.: 514-907-3253 # Sans Frais: 866-507-3253 # Fax.: 1-866-334-1426 Protection de courriel par LastSpam (www.lastspam.com)

I would like to write up brief tutorial/documentation on how to manage /etc/passwd using puppet. While this may seem pretty straight forward to some...the documentation is not. We have been able to create a manifest that defines all of our users "virtually" and are able to "realize" users and add them to the system(s) running puppetd. Is there a way to simply realize all users

Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or

just to let you know: the authentication doesn't work correctly under linux: Nov 29 22:35:06 zobi sshd[11661]: Server listening on 0.0.0.0 port 22. Nov 29 22:35:06 zobi sshd[11661]: Generating 768 bit RSA key. Nov 29 22:35:07 zobi sshd[11661]: RSA key generation complete. Nov 29 22:36:11 zobi sshd[11668]: Failed password for zvo from 127.0.0.1 port 738 Nov 29 22:36:18 zobi sshd[11668]: Failed

On 24/10/2020 15:44, Sonic via samba wrote: > I'm seeing a lot of these errors from a Samba 4.13.0 DC running on > Debian Buster, the smb.conf is untouched from that which was created > via a classic upgrade. > =============================== > Oct 24 10:25:43 srvr01 samba[26688]: [2020/10/24 10:25:43.886363, 0] > ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler)

I'm seeing a lot of these errors from a Samba 4.13.0 DC running on Debian Buster, the smb.conf is untouched from that which was created via a classic upgrade. =============================== Oct 24 10:25:43 srvr01 samba[26688]: [2020/10/24 10:25:43.886363, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) Oct 24 10:25:43 srvr01 samba[26688]: /usr/local/samba/sbin/samba_dnsupdate:

Hello, I wondered how folks monitored slaves. In my case, I am using Nagios and the check_ups plugin. It seems to work fine but being new to nut, I'm seeking confirmation that this is a sane approach. The goal: confirm the slaves have contact with the master. The environment: * FreeBSD 12.1 * nut-2.7.4 installed from package Background: I am replacing an APC 2200 UPS (still in use) with

CentOS Errata and Bugfix Advisory 2020:5035 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5035 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 04343e0c734f4810fb43a53773019eae05e21428fa5cf05b99db8582265dc3d9 mod_auth_openidc-1.8.8-9.el7_9.x86_64.rpm Source:

On Fri, 4 Sep 2020, Dan Langille wrote: > I wondered how folks monitored slaves. A NUT solution is to use a "heartbeat" generated in each slave and monitored in say the master or elsewhere. > The goal: confirm the slaves have contact with the master. On your Github site: Goal: allow host to shutdown when needed. These are not the same goals In NUT, for the shutdown process,

On Wed, 17 Oct 2018 15:03:41 +0200 Giuseppe Sacco via samba <samba at lists.samba.org> wrote: > Hello, > i configured samba and winbind in order to let domain users access > folders shared by samba on linux. The configuration is shown later. > > Please note that idmap is configured correctly: > > root at kubuntu-test:~# wbinfo --user-info 'AGENZIA+manuelb'

On Fri, Sep 4, 2020, at 5:19 PM, Roger Price wrote: > On Fri, 4 Sep 2020, Dan Langille wrote: > > > I wondered how folks monitored slaves. > > A NUT solution is to use a "heartbeat" generated in each slave and monitored in > say the master or elsewhere. I did find this earlier today: https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-April/010590.html Is

Hello, i configured samba and winbind in order to let domain users access folders shared by samba on linux. The configuration is shown later. Please note that idmap is configured correctly: root at kubuntu-test:~# wbinfo --user-info 'AGENZIA+manuelb' AGENZIA+manuelb:*:5035:5002::/home/manuelb:/bin/bash root at kubuntu-test:~# wbinfo -n 'AGENZIA+manuelb'

GPO's fail to apply on Windows clients and sysvol permission errors are logged. DC is Samba 4.13.0 created via a classic upgrade. Logged sysvol errors (uid 5025 is the system I ran gpupdate on, don't know what uid 3000011 refers to): =================================== Oct 25 12:17:09 srvr01 smbd[3762]: [2020/10/25 12:17:09.695062, 0]

Hello. I have problems with duplicate emails when using replication and configured message filters on the client. Looks like when letter comes, it processed by replication and immediately after this processed by filter on client and moved to another folder. When it arrives to slave server into INBOX, it replicated back to master into INBOX and only after that - slave receives MOVE command. The

On 24/10/2020 18:05, Sonic wrote: > On Sat, Oct 24, 2020 at 12:46 PM Sonic <sonicsmith at gmail.com> wrote: >>> Who is user '5035' ? >> No clue, all users have a uidNumber in 1000-1999 with all sids ending >> in 2000-2999. > Sorry that was from the AD side, the same client with the > 192.168.7.176 address has a local unix uid of 5035 - I have not yet

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

On Sat, Oct 24, 2020 at 11:13 AM Rowland penny via samba <samba at lists.samba.org> wrote: > denied access to sysvol and a client is being denied updating its record. > > Does the DC use itself as the first nameserver in /etc/resolv.conf ? Same issue whether or not I point to itself first or to the local cache. > Who is user '5035' ? No clue, all users have a uidNumber

Hi, after we switched to rsyslog with high precision timestamps logcheck did not match the timestamps any more. A patch adding the high precision timestamp format is attached. The rules now match both the traditional timestamp format and the high precision timestamp format (with or without microseconds). Yours sincerely, Ralf D?blitz -- Ralf D?blitz r.doeblitz at asco.de Tel 0531/3906-116

HI ALL: I am newbie to IAX, my iax.conf is as follows: [general] port=5036 ..... but I donot why it doesnot listen on UDP PROT 5035, instead it listens on 4569 Asterisk CLI debug says: [chan_iax2.so] => (Inter Asterisk eXchange (Ver 2)) == Manager registered action IAXpeers == Parsing '/etc/asterisk/iax.conf': Found Nov 30 11:52:12 WARNING[1076220544]: