search for: backdating

Hi List, I have running a Samba Domain PDC and BDC over 2 yeahrs without winbind. In the last time i have some stange failures in the user authority, now my ask can i backdated winbind? MFG Sven

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

Hello, I'm trying to establish a radio station using Icecast but I need a recommendation about a problem. I hope you can give me some tips about the issue. My case is: my icecast server and ice cast client are in different locations and connection between these two is not so healthy. Sometimes network problems causes client to loose connection with server and this causes server to broadcast

Hi everybody, I'm trying to implement in the non profit organization where I work a backup strategy for our VMs. At the moment I weekly backup the machine (on sunday nights) by stopping the vm, making a snapshot, exporting the xml descriptor file and syncing these files to a remote backup server. I would really like to make daily snapshot without shutting down the vms. at the moment the vms

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

That isn't how rsync should work with -a. Is something preventing it from backdating the file? What is the filesystem? Can you try copying your 2015 file with cp -a? On 10/9/24 14:56, McDowell, Blake wrote: > Hi Kevin, > > The -a flag in this instance is not back-dating the timestamp of the > copied file to the source file. It is modifying it to the time of >...

Others have commented on the usefulness of adding an explicit list of what should be included in the kernel. I second that. There''s another thing that''s tripped me up: While iproute2 compiles and installs easily (on a Red Hat 6.1 box), the documentation is in a format that - while not obscure to old Unix hands - requires compilation, which requires: "To make documentation,

How to get rid on following.. why its Invalid ? holler*CLI> queue show queue1 queue1 has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s Members: Agent/7201 (Invalid) has taken no calls yet Agent/7202 (Invalid) has taken no calls yet No Callers -------------- next part -------------- An HTML

On 11/06/2014 03:45 PM, Francesco Morosinotto wrote: > Hi everybody, > > I'm trying to implement in the non profit organization where I work a > backup strategy for our VMs. > > At the moment I weekly backup the machine (on sunday nights) by stopping > the vm, making a snapshot, exporting the xml descriptor file and syncing > these files to a remote backup server.

...rticular volume, when I added the --checksum option, went from 11m37.520s to 290m22.423s. If I could cut that down, this would be a good thing. On the other hand, the reason I'm switching to checksum as opposed to the timestamp approach is to catch files that people are deliberately "backdating" to avoid the changes being seen. I'm unclear how caching checksums doesn't cause exactly that problem (since a cached checksum means that the file isn't checked for changes each time rsync runs). I guess I'm vague on a lot of the ideas around the of checksums. Enlightenm...

Hello, I've got a mixture of SPIP 300 and 500 phones in production for various clients. I've got the XML settings configured for local conferencing, but I'm not seeing the expected behavior from the phone when I attempt to conference two calls together. According to the manual, while talking to the first party, you simply hit Conference, dial the second party and then Conference

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you a lot for your reply; > You should really consider using libvirt live snapshots. With new > enough libvirt and qemu, you can even get optimal behavior with no guest > downtime. This topic comes up frequently on the list; for example, a > quick search found this in the archives: > >

I work for Terra Soft Solutions (makers of Yellow Dog Linux) and I'm trying to compile the latest cvs snapshot for inclusion in our next release, but I'm running into some problems... I'm using modified versions of the SRPMs included in RedHat's Rawhide distro (I only updated to the latest cvs, but the old version also experienced this problem), which compile fine on an x86 box I

I need a pointer in the right direction... Is there a document for migrating puppet/passenger to 3.0? -- Peter L. Berghold Salty.Cowdawg@gmail.com http://blog.berghold.net “"Don''t wait until everything is just right. It will never be perfect. There will always be challenges, obstacles and less than perfect conditions. So what. Get started now. With each

Hi Kevin, The -a flag in this instance is not back-dating the timestamp of the copied file to the source file. It is modifying it to the time of transfer and leaving it that way. Then any time I rerun that command it always updates the timestamp since it is always making it the time of transfer. I have a source file the has a modification date of 2015 and when I rsync it to day with -a the copied

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).