search for: fnish

Hey Jud, Thanks! I copied two of my FLAC folders (CDs) into a temp dir just to test it out and see if I could get it to run. I put the four unzipped files into the dir folder and opened a cmd window using the same options you suggested: "reflac -r -8 -nw -nb" It looks as though it first converts the files to WAV then re-encode them into FLAC 1.1.4 then deletes the WAV, correct? I was

...of course. Brian W. On Apr 11, 2007, at 19:18, Jud White wrote: You're right it decodes to WAV then re-encodes.. it uses flac option "-w" (warnings as error) and checks for error return codes.. if an error occurs it restores the original file and reports the problem when it fnishes or you ^C the program.. After re-encoding it deletes the wav, reads the original FLAC's metadata blocks (minus streaminfo and seektable) and writes them to the new FLAC file.. then it double checks the sample count in both flacs match (just in case), runs "flac -t" on the ne...

You're right it decodes to WAV then re-encodes.. it uses flac option "-w" (warnings as error) and checks for error return codes.. if an error occurs it restores the original file and reports the problem when it fnishes or you ^C the program.. After re-encoding it deletes the wav, reads the original FLAC's metadata blocks (minus streaminfo and seektable) and writes them to the new FLAC file.. then it double checks the sample count in both flacs match (just in case), runs "flac -t" on the new fi...

We are pleased to announce the immediate availability of CentOS-5.11 for i386 and x86_64 Architectures. CentOS-5.11 is based on source code released by Red Hat, Inc. and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an announcement email, not the release notes.

We are pleased to announce the immediate availability of CentOS-5.11 for i386 and x86_64 Architectures. CentOS-5.11 is based on source code released by Red Hat, Inc. and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an announcement email, not the release notes.

...-i eth0 -p udp --dport 1:1024 -j DROP # Close the port of webmin iptables -A INPUT -s 0.0.0.0/0 -i eth0 -p tcp --dport 10000 -j DROP ## FORWARD # Do log all forward iptables -A INPUT -j LOG --log-level info iptables -A OUTPUT -j LOG --log-level info iptables -A FORWARD -j LOG --log-level info ## Fnish of table FILTER ## General of MASQUERADE iptables -t nat -A POSTROUTING -s 172.16.0.6/32 -o eth0 -j MASQUERADE iptables -t nat -A POSTROUTING -s 172.16.0.10/32 -o eth0 -j MASQUERADE #iptables -t nat -A POSTROUTING -s 172.16.0.1/32 -o eth0 -j MASQUERADE iptables -t nat -A POSTROUTING -s 172.16.0.9/...

...cache, e.g. KEYRING:persistent:1003:1003. Suppose I need to kinit as a different user, e.g. hedrick.admin. If KRB5CCNAME is set to the collection, kinit will create a new cache for hedrick.admin, leaving the original one undisturbed, and change the primary cache to the new one. Then when I'm fnished I can go back to hedrick using "kswitch -p hedrick". However if KRB5CCNAME is set to KEYRING:persistent:1003:1003 rather than to KEYRING:persistent:1003, kinit will replace the credentials, and I'll have to kinit again to go back to hedrick. With one-time passwords I'd really ra...