search for: backdat

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

...file, make a snapshot of the subvolume storing the qcow2 file and the resuming the machine back (in I hope less than 10 seconds of downtime). what do you guys suggest me? Am I going to experience bad performance having qcow2 over btrfs? I was reading something like that but the posts were really backdated... any hints is really appreciated Thank you Francesco

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 &g...

...s. I do see the link to an HTML version from 10/23/99 in the HOWTO''s "Further reading" section - but are the docs the same a year later? Maybe the HOWTO should include full quotations of Alexey''s documents so those of us who don''t really care about learning to backdate our systems to include a full suite of obscure Unix typesetting utilities can read the stuff ... and not send stupid questions to this list that those docs answer. I have full respect for those who can typeset beautiful documents on Unix using the legacy tools - it''s just a set of skills...

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

...ausing the VM manually, which is more downtime than you will have if you use libvirt's live snapshot mechanisms. > > what do you guys suggest me? > > Am I going to experience bad performance having qcow2 over btrfs? > I was reading something like that but the posts were really backdated... As far as I know, this is still a real problem unless you manually configure btrfs to not do copy-on-write, at least when qcow2 images are involved. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

...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. Enlight...

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

...ch is more downtime than you will have if > you use libvirt's live snapshot mechanisms. > >> >> what do you guys suggest me? >> >> Am I going to experience bad performance having qcow2 over btrfs? >> I was reading something like that but the posts were really backdated... > > As far as I know, this is still a real problem unless you manually > configure btrfs to not do copy-on-write, at least when qcow2 images are > involved. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRbqxEACgkQWZ6iCY3lmBSOiQCeMG6E60y1CmnCiBA7Ls9DThIx D4sAn...

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).