From chasecreek.systemhouse at gmail.com Mon Jul 11 08:23:07 2005 From: chasecreek.systemhouse at gmail.com (Chasecreek Systemhouse) Date: Mon, 11 Jul 2005 11:23:07 -0400 Subject: [Jax.PM] JaxPM officially declared dead Message-ID: <91f88ee2050711082378e09454@mail.gmail.com> [Admin Posting] JaxPM officially declared dead -- if no one wishes to take over as PM Leader I will contact support at pm.org to nuke the group. Let me know. -- WC -Sx- Jones open source consulting: http://youve-reached-the.endoftheinternet.org/ From chasecreek.systemhouse at gmail.com Fri Jul 29 11:30:34 2005 From: chasecreek.systemhouse at gmail.com (Chasecreek Systemhouse) Date: Fri, 29 Jul 2005 14:30:34 -0400 Subject: [Jax.PM] preventing .bash_history from being deleted Message-ID: <91f88ee205072911305763b6c7@mail.gmail.com> I am curious as to how JaxLUG (and JaxPM) members, especially those that are security minded, handle the shell history tracking? What options are there to prevent: cp /dev/null .bash_history && history -c ??? -- WC -Sx- Jones open source consulting: http://youve-reached-the.endoftheinternet.org/