Tag Info

New answers tagged

0

You can display the contents of a file with cat, but with binary files that will often result in "garbage". For binary files you can use od -x (or xxd): od -x file.bin that makes everything byte readable as hex words for any file (understanding what that means is more difficult and dependent on the program that wrote the file, but fortunately that is not ...


4

openssl's stdin is a byte stream. The contents of $user is a sequence of non-0 bytes (which may or may not form valid characters in UTF-8 or other character set/encoding). printf %s "$user"'s stdout is a byte stream. printf %s "$user" | openssl dgst -sha256 –binary Will connect printf's stdout with openssl's stdin. openssl's stdout is another byte ...


0

Just an PS: on MacOS, Java is usually installed at '/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home', where the version number could be different.


5

You can't store binary data (binary data generally refers to data with arbitrary byte values, not only byte values that form valid characters but is not special otherwise) in bash variables as bash doesn't support storing the 0 byte value in its variables (and remember you can't pass such strings in arguments to commands as those are NUL delimited strings). ...


2

Get rid of the &. That makes it fork into the background, Upstart thinks the process died, then spawns a new one. Just have the exec line without the ampersand.


2

There's no point in having them both in $PATH because only one will get used. You could symlink one to a different name -- e.g. java6 -- I've never tried this w/ java and not sure if it would work. The best way to do this would be to install one of them (presumably 1.6) in a location like /opt/java6, leaving 1.7 as the default. Then when you want to use ...


0

I finally could use RxTx library thanks to the (64 bits) librxtxSerial.so driver found at http://jlog.org/rxtx-lin.html . Before that I was getting below error, probably due to a bad librxtxSerial.so file (32 bit version or bad 64bits file?). # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fb9b0249462, ...


0

The issue is Resolved. It turn out to be that the labeling of the file related to java(both openjdk and oracle java) was not correct in my redhat 6 system. When i upgraded from redhat 6 to redhat 7 it started working all fine i.e sandbox java -version worked perfectly with no problems. In my redhat 7 system the .so and other java related file are labeled ...



Top 50 recent answers are included