Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14350
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: About bash_syslog_histrory Function! |
| Date | 2018-07-17 11:02 -0400 |
| Message-ID | <mailman.3714.1531839776.1292.bug-bash@gnu.org> (permalink) |
| References | <20180717160301394028110@unionpay.com> |
On 7/17/18 4:03 AM, sunhuilin@unionpay.com wrote: > Hi: > I found the orginal bash_syslog_history has three flaws: > 1、 Ingore the texts that length exceed SYSLOG_MAXLEN,however in our environment ,we have a lot of db2 command line which exceed SYSLOG_MAXLEN; > 2、only get PID and UID, lack some import information such as tty,orginal host ,user info ... > 3、only by compile with SYSLOG_HISTORY=1 ,which is not default. Is there any possible that by active it by default or where env parameter BASH_SYSLOG_HISTORY is set to on ? > > would you please consider improve about it ? I will look at your line continuation code, but I am not interested in making something I consider an invasion of privacy enabled by default. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: About bash_syslog_histrory Function! Chet Ramey <chet.ramey@case.edu> - 2018-07-17 11:02 -0400
csiph-web