Command Line looking wrong - command

My command line looks like this:
|system||system|ruby 2.0.0p645 (system) User_name-MacBook-Air in ~
Can someone tell me how to edit this down to:
User_name-MacBook-Air in
I have a feeling it has to do with a recent RVM issue I was having, but any help on cutting down
|system||system|ruby 2.0.0p645 (system)

Related

Need help to write a basic Command Line code

I'm using Windows 10 if it matters and I'm trying to feed a file to the "oeminst" app that will convert this file from .EDR to .CCSS. According to the app's website its usage summary is this:
oeminst [-options] [inputfiles]
-v Verbose
-n Don't install, show where files would be installed
-c Don't install, save files to current directory
-S d Specify the install scope u = user (def.), l = local system]
infile Manufacturers setup.exe install file(s) or .dll(s) containing install files
infile.[edr|ccss|ccmx] EDR file(s) to translate and install or CCSS or CCMX files to install
If no file is provided, oeminst will look for the install CD.
more info can be found here https://www.argyllcms.com/doc/oeminst.html
So far I tried this code:
C:\Users\PC>oeminst infile. [C:\Users\PC\testfile.edr]
oeminst: Error - Unable to load file 'infile [C:\Users\PC\testfile]'
I'd appreciate if someone at least could tell me if I'm doing it right or not.
P.S. sorry for the messed up text. Not sure how to fix it. It looks good in editing mode.
Try this : oeminst infile.edr C:\Users\PC\testfile.edr
Nevermind, I got it.
C:\Users\PC>oeminst C:\Users\PC\testfile.edr

WinDbg script not working

I often need to type in a bunch of .srcpath+, .sympath+, and .exepath+ to load paths in order to debug a crash dump. I like to put these settings into a script file so to make my life easier. From the command I tried:
$$>< E:\Supports\envs.wdb
I got errors:
The filename, directory name, or volume label syntax is incorrect
for each line I added in the script. But If entered the lines manually, everything was fine.
I also tried to run windbg.exe -c "$$>< E:\Supports\envs.wdb", and I got the same errors.
Any helps would be greatly appreciated.
Btw, I like to put each path in a separate line so I can quickly edit paths in the script using block mode. With mainactual's help, debugging a crash dump becomes very quick for me. :)
Path commands are bit tricky since the syntax is
.srcpath[+] [directory [; ...]]
which makes command
.srcpath C:\Foo
.srcpath+ C:\Bar
to be interpreted as a single line command
.srcpath C:\Foo;.srcpath+ C:\Bar
To work around this, use "-marks
.srcpath "C:\Foo"
.srcpath+ "C:\Bar"
or
.srcpath "C:\Foo;C:\Bar"
And notice also that you don't need "-marks for white space:
.srcpath "C:\Foo Bar;C:\Bar"

sed command is not working properly

I'm trying to replace the word in shell script with sed -e command but its not replacing , please help on that, i have tried the below
we have separate file in /data/docs/config.log, in that file there is a word ?account for example ,
username acc, passsword acc, ?account.name
this ?account word needs to be replaced with word 'GLOBAL' using sed -e command ,
reacc = GLOBAL
sed -e "s/?account/$reacc/g" /data/docs/config.log > /data/docs/newconfig.log
but here the file newconfig.log has created with 0 size , no output written to the file , its not replacing its an empty file,
the output should be username acc, passsword acc, GLOBAL.name in newconfig.log
Being the only person who can reproduce the problem, you are pretty much on your own. There are plenty of things you can do to analyze the problem, though.
Double-check the shell. Don't have blind faith in #!/bin/sh. In cygwin for example, /bin/sh is an alias for bash. Verify with: echo $SHELL
Check permissions and file system. Do you have rights to write to the output file? Is the disk full? Does cat /data/docs/config.log > /data/docs/newconfig.log work? Test again in a different folder.
Double-check the output file. Is it really empty, or is the file system just slow with updating the file size? Is sed really finished? Test without output redirection; see if the output is dumped to stdout.
Test with a small file; one or two lines is enough.
If even that does not work, then test sed itself. Who knows, maybe you have a weird alias that hides the real sed. The most trivial filter is sed -e '', which should simply echo every line you type (just like cat without parameters). Does that work? Then try some simple patterns.
Systematically iterate between test cases that succeed and test case that fail, until you have found the breaking point. Doing so, you should be able to find the cause. Sorry, that's all I can do for you right now.
Remove spaces around =. Try after making
reacc=GLOBAL

export PATH creating a redundant path

I need to add some perl scripts to PATH, but when I do, and try to run the scripts, it can't find the files. For some reason it is using a redundant path and doesn't find it. I dont know how to describe the problem but the code is pretty self-explanatory.
[lsk250#murphy portfolio-handout]$ pwd
/home/lsk250/portfolio-handout
[lsk250#murphy portfolio-handout]$ export PATH=$PATH:/home/lsk250/portfolio-handout/
[lsk250#murphy portfolio-handout]$ time_series_symbol_project.pl
env: /home/lsk250/portfolio-handout//home/lsk250/portfolio-handout/get_data.pl: No such file or directory
sh: line 1: 17758 Aborted (core dumped) time_series_project _data.in 8 AWAIT 300 ARIMA 2 1 2 2> /dev/null
Any ideas whats the right export command I should use to get this right?
There is nothing wrong in how you export PATH variable except that you may already have your "pwd" there.
As far as I can see the get_data.pl is called from time_series_symbol_project.pl (or from some other script called from time_series_symbol_project.pl and so on) and I would check how it is called.
Perhaps you could also see if PATH is changed somewhere in your scripts.
i'm guessing the "shebang" line (#!) and/or file permissions on 'get_data.pl' is incorrect.

Unsure of how to proceed with creating ec2-consisten-snapshot

I was just put on a task to try and debug and figure out why our ec2-consistent-snapshot script isn't working.
Our lead programmer followed this blog post.
We have a .sh script that we'd like to take the snapshot and it looks like this:
#!/bin/sh
/opt/aws/bin/ec2-consistent-snapshot --aws-access-key-id MYACCESSKEY --aws-secret-access-key MYSECRETKEY --freeze-filesystem /vol --mysql --mysql-host localhost --mysql-socket /var/lib/mysql/mysql.sock --mysql-username USERNAME --mysql-password PASSWORD --description "Demo MySQL data volume: $(date +%c)" vol-MYVOL
If I run this by doing sudo ./snapshot_script.sh I get a single error:
ec2-consistent-snapshot: ERROR: create_snapshot: File does not exist: at /usr/share/perl5/vendor_perl/Net/Amazon/EC2.pm line 232
I of course followed this error and line 232 in EC2.pm is this:
my $ref = $xs->XMLin($xml);
I have 0 perl experience and I don't know what this could be doing.
Any help would be wonderful.
The Net::Amazon::EC2 that I'm looking at on CPAN has that line at 252, not 232 so perhaps you are not on the latest version. Looking above that line, the program has attempted to do a "query to sign" using lots of the security parms. I suspect there is a problem with the authentication keys you are using. There is a debug flag, you might want to turn that on to generate more messages.
If you go to this page, you will see that XMLin() is a function of XML::Simple, and it takes a file as an argument. So, $xml is presumably a variable that contains an xml file name. That file does not exist.
The next step would be to trace the error back into the source code of ec2-consistent-snapshot, in order to see how it is calling XML::Simple and where the bad value gets passed in.