Reputation
384
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 12
Newest
 Curious
Impact
~88k people reached

  • 0 posts edited
  • 1 helpful flag
  • 27 votes cast
Jul
21
comment ssh without using the user's default shell
I dunno why I didn't upvote this question. While it didn't satisfy my needs, it's still potentially valuable to someone else.
Jul
21
accepted bash: history -a not writing unless HISTFILE already has text
Jul
18
awarded  Curious
Jul
17
revised bash: history -a not writing unless HISTFILE already has text
Trying to use a code block inside a block quote, but the language spec isn't applying to the code block.
Jul
17
revised bash: history -a not writing unless HISTFILE already has text
added 47 characters in body
Jul
17
revised bash: history -a not writing unless HISTFILE already has text
added 779 characters in body
Jul
17
asked bash: history -a not writing unless HISTFILE already has text
Jul
17
answered bash: history -a not writing unless HISTFILE already has text
Jun
2
answered How do I run this `find` command, but only on non-binary files?
Jun
2
answered How to find Binary file in solaris?
Jun
2
revised Equivalent of “du --max-depth=0 -h” (or something similar) in Solaris
added 238 characters in body
Jun
1
awarded  Self-Learner
Apr
29
comment rsync functionality wanted - but i need symlinks, not copies
Two things I left out: 1) cp -s is only able to do relative symlinks if copying into the same directory, and 2) the cp command in my modification requires an eval.
Apr
29
comment rsync functionality wanted - but i need symlinks, not copies
note also that cp -l makes hard links, whereas cp -s makes symlinks. If the tree is large and the 2nd option ends up being at all slow, it could also be accomplished with something along the lines of: for i in $(cd srcdir; find . -mindepth 1 -type d -printf '"%p" '); do mkdir -p "dstdir/${i}"; cp -l $(find "srcdir/${i}" -maxdepth 1 -not -type d -printf '"%p" ') "dstdir/${i}".
Apr
16
comment ssh without using the user's default shell
That was one of the more irritating aspects of this problem. If the user's default shell is bash it wasn't difficult at all to avoid having .bashrc get sourced. csh and tcsh, on the other hand, are a little more irritating.
Apr
16
accepted ssh without using the user's default shell
Apr
16
comment ssh without using the user's default shell
@DonSimon, You're correct. I'm fairly sure that was my last option. Although it sucks, that seems like an acceptable answer if you want to post it as such.
Apr
16
revised ssh without using the user's default shell
added 856 characters in body
Apr
16
revised ssh without using the user's default shell
added 856 characters in body
Apr
16
comment ssh without using the user's default shell
If you're going to downvote, the least you could do is provide some form of criticism.