bpdbjobs -report AHHHH!!!! 1

[froggger]

Can anyone explain why the bpdbjobs report show \\ (double back slashes) in the report for windows client only. Unix client file paths appear normal.
Example : Windows
61089,0,3,0,TOR-Win,Differential-Inc,tor1-ctrx1,tac-nbu1,1110945948,0000000583,1110946531,tac-nbu1-hcart-robot-tld-0,1,,369741,2355,,100,23988,root,1,13,1,1,,tac-ovcs3,2,3,0,,,2,C:\\,,1,23988,tac-nbu1-hcart-robot-tld-0,tac-nbu1,1110945959,0000000572,1110946531,0,the requested operation was successfully completed,9,03/15/05
Example unix :
61091,0,3,0,oracle-ovsd,Auto-Inc,10.253.20.25,tac-nbu1,1110945948,0000000386,1110946334,tac-nbu1-hcart-robot-tld-0,1,,,,,100,23995,root,1,4,1,0,,tac-ovcs3,2,3,0,,,1,/opt/sd/admin/orabackup/dbbk.sh,1,23995,tac-nbu1-hcart-robot-tld-0,tac-nbu1,1110945960,0000000374,1110946334,0,the requested operation was successfully completed,4,03/15/05 23:06:01

 

[zereack]

UNIX uses / windows uses \

because \ is an escape char in every os/laung except M$ you run into problems when you want to do a literal \ , you need to escape the escape char .. so you get \\ ... same thing happens when you want to quote a string in a string so

"bob said "hello""
would need to be written like
"bob said \"hello\""

it does a C:\\, because a C:\, would mean the , is part of the path and not part of the separator ( i.e. the comma would be escaped ) so C:\, actually = C:, as a path where C:\\, = C:\ as the path and , as the end of that column.

the fact that the bpdbjobs does this is actually helpfull when useing perl or other programing launagues to parse the output as it would really mess it up otherwise .. but sometimes it can be a hassle also.

that help to explaine it?