03-10-2022 06:46 AM
All,
I found a file on my BYO NetBackup Linux Master server whos name was simply a comma. The contents of the file is as follows.. Can anyone identify this file from its contents? File was found in a users home directory.
Thanks in advance
Solved! Go to Solution.
03-10-2022 06:20 PM
It's almost certainly the result of a mistake with the options to an "awk" command. The file is what is created by awk when you use the "-d" option (dump variables).
What the user was trying to do, is another matter. They could have been intending to use cut rather than awk (i.e. cut -d,) to filter some output but typed awk instead, or use the -d option thinking it has the same meanaing with awk as it does for cut. etc.....
Definitely not worth worrying about (unless you want to educate your users) and not from NetBackup.
Cheers
David
03-11-2022 01:45 AM
Agree with David, Stefanos and Jeff. Looks like a file created by a misbehaving script.
/Nicolai
03-10-2022 07:13 AM
The files doesn't have a Veritas look and feel look to it. What was the file called in the users home directory ?
/Nicolai
03-10-2022 07:23 AM
I agree.. The filename was a comma Nicolai.. Just a comma.. Nothing else. I have deleted the file already but took a screenshot of the contents before I did. I can see awk related entities in there and I'm wondering if this is a file that may have been placed to set variables to another script that may be parsing the messages file.
03-10-2022 07:29 AM
03-10-2022 07:36 AM
well , I'm used to find strange files to my servers.
Some times I make typo errors to my scripts and send the output to files with funny names. Like @," etc...
03-10-2022 08:01 AM
Same here Stefanos.. Done that myself. I don't think this is anything to be concerned with but I would just like to make sure.
03-10-2022 06:20 PM
It's almost certainly the result of a mistake with the options to an "awk" command. The file is what is created by awk when you use the "-d" option (dump variables).
What the user was trying to do, is another matter. They could have been intending to use cut rather than awk (i.e. cut -d,) to filter some output but typed awk instead, or use the -d option thinking it has the same meanaing with awk as it does for cut. etc.....
Definitely not worth worrying about (unless you want to educate your users) and not from NetBackup.
Cheers
David
03-11-2022 01:45 AM
Agree with David, Stefanos and Jeff. Looks like a file created by a misbehaving script.
/Nicolai
03-11-2022 05:52 AM
Thanks David... Thought so too. Just wanted to see what everyone else here thought about it.