Modifying .bashrc to send history to syslog, problems with quotes
Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc
This works if I manually edit .bashrc:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'
Adding awk '{print $1}' causes problems, I suspect because of quotes.
This doesn't work:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'
Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.
Any suggestions on both of these issues?
bash ubuntu bashrc
asked Jan 27 at 7:16
Alex RAlex R
11
add a comment |
Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc
This works if I manually edit .bashrc:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'
Adding awk '{print $1}' causes problems, I suspect because of quotes.
This doesn't work:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'
Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.
Any suggestions on both of these issues?
bash ubuntu bashrc
asked Jan 27 at 7:16
Alex RAlex R
11
2
Why don't you write a shell function and call that fromPROMPT_COMMAND? Why do youexport PROMPT_COMMAND?
– Kusalananda
Jan 27 at 8:10
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
Well, in that case, don't put single quotes inside a single quoted string (see theawkbit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside ofPROMPT_COMMANDbefore even setting that variable.
– Kusalananda
Jan 27 at 18:29
add a comment |
Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc
This works if I manually edit .bashrc:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'
Adding awk '{print $1}' causes problems, I suspect because of quotes.
This doesn't work:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'
Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.
Any suggestions on both of these issues?
bash ubuntu bashrc
asked Jan 27 at 7:16
Alex RAlex R
11
Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc
This works if I manually edit .bashrc:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'
Adding awk '{print $1}' causes problems, I suspect because of quotes.
This doesn't work:
export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'
Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.
Any suggestions on both of these issues?
bash ubuntu bashrc
bash ubuntu bashrc
asked Jan 27 at 7:16
Alex RAlex R
11
asked Jan 27 at 7:16
Alex RAlex R
11
asked Jan 27 at 7:16
Alex RAlex R
11
asked Jan 27 at 7:16
Alex RAlex R
11
asked Jan 27 at 7:16
Alex RAlex R
11
11
2
Why don't you write a shell function and call that fromPROMPT_COMMAND? Why do youexport PROMPT_COMMAND?
– Kusalananda
Jan 27 at 8:10
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
Well, in that case, don't put single quotes inside a single quoted string (see theawkbit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside ofPROMPT_COMMANDbefore even setting that variable.
– Kusalananda
Jan 27 at 18:29
add a comment |
2
Why don't you write a shell function and call that fromPROMPT_COMMAND? Why do youexport PROMPT_COMMAND?
– Kusalananda
Jan 27 at 8:10
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
Well, in that case, don't put single quotes inside a single quoted string (see theawkbit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside ofPROMPT_COMMANDbefore even setting that variable.
– Kusalananda
Jan 27 at 18:29
2
2
Why don't you write a shell function and call that from
PROMPT_COMMAND? Why do you export PROMPT_COMMAND?– Kusalananda
Jan 27 at 8:10
Why don't you write a shell function and call that from
PROMPT_COMMAND? Why do you export PROMPT_COMMAND?– Kusalananda
Jan 27 at 8:10
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
Well, in that case, don't put single quotes inside a single quoted string (see the
awk bit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside of PROMPT_COMMAND before even setting that variable.– Kusalananda
Jan 27 at 18:29
Well, in that case, don't put single quotes inside a single quoted string (see the
awk bit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside of PROMPT_COMMAND before even setting that variable.– Kusalananda
Jan 27 at 18:29
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496975%2fmodifying-bashrc-to-send-history-to-syslog-problems-with-quotes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496975%2fmodifying-bashrc-to-send-history-to-syslog-problems-with-quotes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Why don't you write a shell function and call that from
PROMPT_COMMAND? Why do youexport PROMPT_COMMAND?– Kusalananda
Jan 27 at 8:10
@Kusalananda, I attempted to create a function as this seemed like the correct way to do this. Unfortunately ended up breaking bashrc and temporarily locking myself out of the VM. The single line command seemed easier.
– Alex R
Jan 27 at 18:18
Well, in that case, don't put single quotes inside a single quoted string (see the
awkbit). Doing it as a function would allow you to write readable code that doesn't have to use quoting tricks. It would also allow you to test it outside ofPROMPT_COMMANDbefore even setting that variable.– Kusalananda
Jan 27 at 18:29