Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

backup - rsync - what means the f+++++++++ on rsync logs? -


i'm doing rsync make backup of server files, , have 2 questions:

1 - on middle of proccess need stop , start again rsync, i'd know if rsync start @ same point stoped or restart sync?

2 - on log files show string files "f+++++++++", i'd know means?

eg:

010/12/21 08:28:37 [4537] >f.st...... iddd/logs/website-production-access_log 2010/12/21 08:29:11 [4537] >f.st...... iddd/web/website/production/shared/log/production.log 2010/12/21 08:29:14 [4537] .d..t...... iddd/web/website/production/shared/sessions/ 2010/12/21 08:29:14 [4537] >f+++++++++ iddd/web/website/production/shared/sessions/ruby_sess.017a771cc19b18cd 2010/12/21 08:29:14 [4537] >f+++++++++ iddd/web/website/production/shared/sessions/ruby_sess.01eade9d317ca79a 

thanks.

let's take @ how rsync works , better understand cryptic result lines:

1 - huge advantage of rsync after interruption next time continues smoothly.

the next rsync invocation not transfer files again, had transferred, if not changed in meantime. start checking files again beginning find out, not aware had been interrupted.

2 - each character code can translated if read section -i, --itemize-changes in man rsync

decoding example log file question:

>f.st......

> - item received f - regular file s - file size different t - time stamp different 

.d..t......

. - item not being updated (though might have attributes      being modified) d - directory t - time stamp different 

>f+++++++++

> - item received f - regular file +++++++++ - newly created item 

the relevant part of rsync man page:

-i, --itemize-changes

requests simple itemized list of changes being made each file, including attribute changes. same specifying --out-format='%i %n%l'. if repeat option, unchanged files output, if receiving rsync @ least version 2.6.7 (you can use -vv older versions of rsync, turns on output of other verbose mes- sages).

the "%i" escape has cryptic output 11 letters long. general format string yxcstpoguax, y replaced type of update being done, x replaced file-type, , other letters represent attributes may output if being modified.

the update types replace y follows:

  • a < means file being transferred remote host (sent).
  • a > means file being transferred local host (received).
  • a c means local change/creation occurring item (such creation of directory or changing of symlink, etc.).
  • a h means item hard link item (requires --hard-links).
  • a . means item not being updated (though might have attributes being modified).
  • a * means rest of itemized-output area contains message (e.g. "deleting").

the file-types replace x are: f file, d directory, l symlink, d device, , s special file (e.g. named sockets , fifos).

the other letters in string above actual letters output if associated attribute item being updated or "." no change. 3 exceptions are: (1) newly created item replaces each letter "+", (2) identical item replaces dots spaces, , (3) unknown attribute replaces each letter "?" (this can happen when talking older rsync).

the attribute associated each letter follows:

  • a c means either regular file has different checksum (requires --checksum) or symlink, device, or special file has changed value. note if sending files rsync prior 3.0.1, change flag present checksum-differing regular files.
  • a s means size of regular file different , updated file transfer.
  • a t means modification time different , being updated sender’s value (requires --times). alternate value of t means modification time set transfer time, happens when file/symlink/device updated without --times , when symlink changed , receiver can’t set time. (note: when using rsync 3.0.0 client, might see s flag combined t instead of proper t flag time-setting failure.)
  • a p means permissions different , being updated sender’s value (requires --perms).
  • an o means owner different , being updated sender’s value (requires --owner , super-user privileges).
  • a g means group different , being updated sender’s value (requires --group , authority set group).
  • the u slot reserved future use.
  • the a means acl information changed.
  • the x means extended attribute information changed.

one other output possible: when deleting files, "%i" output string "*deleting" each item being removed (assuming talking recent enough rsync logs deletions instead of outputting them verbose message).


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -