| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 8 months |
| seen | Apr 21 at 3:52 | |
| stats | profile views | 43 |
|
Oct 1 |
comment |
Bash history with timestamps Copied that HISTTIMEFORMAT='%b %d %I:%M:%S %p ' verbatim, still no luck. If I echo $HISTTIMEFORMAT it's the right value. This is interesting! |
|
Oct 1 |
revised |
Bash history with timestamps added 55 characters in body |
|
Oct 1 |
comment |
Bash history with timestamps I most definitely did. It is doing "something": adding a commented line before the command with a numeric timestamp: #1349057149 |
|
Oct 1 |
comment |
Bash history with timestamps Nope, doesn't work on OSX.. :( Prob that's the issue. A strange OS. |
|
Oct 1 |
revised |
Bash history with timestamps added 205 characters in body; edited tags |
|
Oct 1 |
comment |
Bash history with timestamps Probably I am getting the strftime format wrong. It would help if the man page included at least a couple of examples.. +%Y-%m-%d %H-%M-%S ? |
|
Oct 1 |
asked | Bash history with timestamps |
|
Sep 27 |
comment |
Quickly check whether many network hosts are up-and-running @Serge: OSX man ping: developer.apple.com/library/mac#documentation/Darwin/Reference/… |
|
Sep 27 |
comment |
Quickly check whether many network hosts are up-and-running @Serge: sorry, fixed. BTW, on OSX -t is "Specify a timeout, in seconds, before ping exits regardless of how many packets have been received" |
|
Sep 27 |
revised |
Quickly check whether many network hosts are up-and-running added 2 characters in body |
|
Sep 27 |
revised |
Quickly check whether many network hosts are up-and-running deleted 1 characters in body |
|
Sep 27 |
asked | Quickly check whether many network hosts are up-and-running |
|
Sep 12 |
comment |
Am I using bash after this ordeal? Nothing specifically, although this requires interactivity at the console? The question remains: if I su to root from my account, BASH_* variables are exported although I switch to sh. How to correctly detect the shell? $0? Other? |
|
Sep 12 |
comment |
Am I using bash after this ordeal? @Mat: I quote you "make sure it has the right #! line", that "making sure" doesn't do anything; as explained. The line is ignore as a comment. Try it. |
|
Sep 12 |
comment |
Am I using bash after this ordeal? @ire_and_curses: same problem with sudo -i; try echo ${!BASH*} to see the exported bash-specifics still visible as root... |
|
Sep 12 |
comment |
Am I using bash after this ordeal? Careful @Mat! The #! line bears no correlation here as you are effectively source calling your script if you prepend bash explicitly! Try by entering #!/opt/local/bin/perl there and see. That line is only checked when chmod +x executing the file! |
|
Sep 12 |
asked | Am I using bash after this ordeal? |
|
Sep 2 |
comment |
Bash function to compare two binary files @Gilles: I did not know about fdupes! Thanks for the pointer! |
|
Sep 2 |
accepted | Bash function to compare two binary files |
|
Sep 2 |
comment |
Bash function to compare two binary files Interesting. Well, I learned something today! Thanks! BTW, @Stabledog, md5 is because I may want to look for duplicates in a dir tree so I need to keep track of the hashes as I go along to detect pairs to go back to and bit-by-bit scan... Does it make sense? |