-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Quick fix for [ character in prod.txt
- Loading branch information
Engin Eren
committed
May 10, 2016
1 parent
3e8a77e
commit cf3077b
Showing
1 changed file
with
7 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cf3077b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even for a quick fix, would be better make it nicer than search for "[". This should make it solution for good I believe:
Could you incorporate this kind of regexp into your code? Or something along that example should do it...
cf3077b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Marian,
Before implementing, I would like to understand.. If you look at here :
xrdmapc --list all cms-xrd-transit.cern.ch:1094
0**** cms-xrd-transit.cern.ch:1094
...... .....
Srv [::ffff:136.145.164.182]:1094
............
Srv lyogrid06.in2p3.fr:11001
Your example code tells me that this strange hostname (::ffff:136.145.164.182) is ipv4. Yes, it makes sense but
cf3077b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for late answer:
-Marian
cf3077b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been understood and implemented properly, @EnginEren? Have you tested we can recognize IPv6 vs IPv4 entries and parse accordingly? Just trying to see what issues are still pending and which one we can close as resolved... Thanks.