Cybersecurity

Originally Posted by vampirodolce

Hi Reboot,
for some reason when I use script (/usr/bin/script) in .bashrc, as soon as the user logs in the shell goes crazy (e.g. CPU 100%) and the output file - typescript in my case - becomes huge. Do you know why?
The command 'script' on a command line works just fine, it's the .bashrc that doesn't like it. I am using Debian Etch.

Originally Posted by jim mcnamara

As an answer to the original problem try something like this in /etc/profile

Code:

    RU=`who am i | cut -f 1 -d " "`
    if [[ $RU = "root" ]]
      then
        HISTFILE=/someplace_safe/.ihist/.sh_hist_$RU_$$
        HISTSIZE=1000
        export HISTFILE HISTSIZE
      else
        HISTFILE=/$HOME/.sh_history
        HISTSIZE=1000
        export HISTFILE HISTSIZE
    fi

This creates a history file for each root login, the mtime of the file gives you a clue as to which "root" login you are dealing with.

Originally Posted by Reboot

Could you show the entries (or commands) you are putting in /.bashrc file......

debian@localhost:100%~$ cat .bashrc|grep ^[^#]

[ -z "$PS1" ] && return
export HISTCONTROL=ignoredups
shopt -s checkwinsize
[ -x /usr/bin/lesspipe ] && eval "$(lesspipe)"
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
case "$TERM" in
xterm-color)
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
;;
*)
PS1='${debian_chroot:+($debian_chroot)}\u@\h:$(echo $(acpi)|/usr/bin/cut -f4 -d\ |cut -f1 -d,)\w\$ '
;;
esac
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007"'
;;
*)
;;
esac
if [ "$TERM" != "dumb" ]; then
eval "`dircolors -b`"
alias ls='ls -F --color=auto'
fi
if [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
umask 077
MAIL=~/Maildir
export MAIL
HISTFILESIZE=400
export HISTFILESIZE
HISTSIZE=400
export HISTSIZE

Snoopy is designed to aid the task of a sysadmin by providing a log of commands executed. Snoopy is completely transparent to the user and applications. It is linked into programs to provide a wrapper around calls to execve(). Logging is done via syslogd

Originally Posted by Reboot

Hi...
First see wether all perameters which you want to change through ~/.bashrc file, changes as per your requirement.In short wether all commands (Excluding '/usr/bin/script ) in ~/.bashrc file work fine......

If yes then just put the '/usr/bin/script -q ~/file.log' command at the very last line of your ~/.bashrc file and then see wether it works or not....

Do not put the '/usr/bin/script -q ~/file.log' command at begining or anywhere in between the ~/.bashrc file .

Hope it should work this time now.....

Cheers....