On Wed, 11 Apr 2001, Kenneth Vestergaard Schmidt wrote:
My first grievance was, that my mail-logs quickly filled up with duplicate
information. Also, some of my other log-files seemed to contain a lot of
duplicate entries. So, I started reading the syslog.conf manpage, and
actually got a
On Wednesday 11 April 2001 13:21, Giacomo Mulas wrote:
I want a good signal to noise ratio and I want to know exactly where I
should look to find a specific kind of log entry.
So a README to the "new" syslog.conf :)
If you have grand plans, I have a suggestion for you: prepare a set of
On Wednesday 11 April 2001 15:03, Christian Hammers wrote:
For this reason (to stay on topic) logging should at least keep the current
behaviour to have one log where everything is logged to, as it's now with
/var/log/syslog. And maybe the /var/log/auth.log with stuff that most
people may
On Wed, Apr 11, 2001 at 03:29:16PM +0200, Kenneth Vestergaard Schmidt wrote:
Why? I think it is really wasted when everything is logged to syslog, and
also logged to other, more specific files. If you want to search for
Maybe people what to archive syslog for a year and the others only for a
On Tue, Apr 10, 2001 at 08:08:02PM -0400, Doug Alcorn wrote:
ipchains -A output -i $ext_interface -p udp -s $your_ip_address
$unprivaleged_ports -d $nameserver_ip 53 -j ACCEPT
ipchains -A input -i $external_interface -p udp -s $nameserver_ip 53
-d $your_ip_address $unprivaleged_ports -j
I discovered what it was.
205.188.153.99 is one of mirabilis icq servers.
The logs were the packets of the messages that I received in GnomeICU :-)
Now I think there isn't much to worry about...
Sorry for asking such a stupid question.
Pedro
On Wed, Apr 11, 2001 at 11:00:30AM -0400, Nick
Neato. That's 3 people in total who think it's a good idea.. :/
It's probably the 3 people in total who bother to check the logs...
make that 4. I always have an xterm with a tail -f /var/log/syslog running
so I can see what is happening to the system. I have a firewall setup but
I don't
Here is another one who bother to check the logs :)
Cheers,
Cristian
On Wed, 11 Apr 2001, JonesMB wrote:
Neato. That's 3 people in total who think it's a good idea.. :/
It's probably the 3 people in total who bother to check the logs...
make that 4. I always have an xterm with a tail
On Wed, Apr 11, 2001 at 02:50:45PM -0700 , [EMAIL PROTECTED] wrote:
Tracking "unstable".
Problems with OpenSSH.
OpenSSL version mismatch. Built against 90600f, you have 90601f
What package[s ] needs to be downgraded?
libssl0.9.6 or recompile ssh
Petr
On Wed, Apr 11, 2001 at 02:50:45PM -0700, [EMAIL PROTECTED] wrote:
OpenSSL version mismatch. Built against 90600f, you have 90601f
I fixed this problem by fetching the source packages for ssh and
building them locally ('apt-get source -b ssh').
noah, who still wishes the *open*ssh packages
I noticed this the other day. I compared two of my servers and found that
this combination works:
ii libssl0.9.60.9.6-2SSL shared libraries
ii ssh2.5.2p2-1 Secure rlogin/rsh/rcp replacement
(OpenSSH)
The latest libssl is 0.9.6a-1, which will give you the version
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Trying to build from source package, but this depends on gnome libs.
YUK
[EMAIL PROTECTED]
On Wed, Apr 11, 2001 at 06:17:53PM -0400, hpknight wrote:
I noticed this the other day. I compared two of my servers and found that
On Wed, Apr 11, 2001 at 04:15:59PM -0700, [EMAIL PROTECTED] wrote:
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Trying to build from source package, but this depends on gnome libs.
Yes, just edit debian/rules in the ssh source and remove the
'--with-gnome' or whatever it is
My machine that got hammed with this needs the pam dev libs (obviously)
but there's a dependency problem with those right now in Sid, so I'm
waiting... (sigh).
On Wed, Apr 11, 2001 at 04:15:59PM -0700, [EMAIL PROTECTED] wrote:
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Somebody mentioned on here that they always have an open terminal
running tail -f /var/log/syslog. I thought that I might try doing
this, but since /var/log/syslog is only readable by root, I decided to
try setting up sudo. I also want access to any log in /var/log. This
is what I have so far:
On Thu, Apr 12, 2001 at 12:49:32AM +, Jim Breton wrote:
On Thu, Apr 12, 2001 at 12:38:10AM +, Adam Olsen wrote:
So my question: how do I set this up properly?
Not with sudo. ;)
chgrp adm /var/log/syslog # change group of file to "adm"
adduser (yourself) adm # put yourself into
On Wed, Apr 11, 2001 at 01:40:13PM -0500, JonesMB wrote:
make that 4. I always have an xterm with a tail -f /var/log/syslog running
so I can see what is happening to the system. I have a firewall setup but
I don't know if it is good enough so I usually monitor the syslog file for
So my question: how do I set this up properly?
edit /etc/syslog.conf
add
*.*/dev/tty8
Kelly Steinmeyer
Linux Systems Administrator
Information Technology Services
Cameron University
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
Followup...
I was successfully able to fix the dependency problems with apt-get,
dselect was being too strict. Or apt-get was being too lenient... :)
On Wed, Apr 11, 2001 at 05:54:57PM -0600, Nate Duehr wrote:
My machine that got hammed with this needs the pam dev libs (obviously)
but
Adam Olsen wrote:
On Thu, Apr 12, 2001 at 12:49:32AM +, Jim Breton wrote:
On Thu, Apr 12, 2001 at 12:38:10AM +, Adam Olsen wrote:
So my question: how do I set this up properly?
Not with sudo. ;)
chgrp adm /var/log/syslog # change group of file to "adm"
adduser (yourself)
On Thu, Apr 12, 2001 at 01:10:17AM +, Adam Olsen wrote:
And for the record, is there any way to get sudo working?
No, not really. What you would have to do would be write a wrapper
script which verifies that all arguments are sane. Deny lists in sudo
are known to be mostly a non-feature.
On Wed, Apr 11, 2001 at 10:10:38PM -0700, Jamie Heilman wrote:
Dan Bernstein's multilog program is the only logger I've seen that offers
various reliability guarentees and actually delivers on them, but it has
some prerequisites for usage that can frequently be difficult to meet.
What I'd
Jim Breton wrote:
Some such solutions are intermittently discussed, designed, etc. on the
[EMAIL PROTECTED] list. Suggest you subscribe and hang out for a while.
:)
http://cr.yp.to/lists.html
Really? See now I've just been browsing archives and I didn't see anything
so I figured
On Wed, Apr 11, 2001 at 09:04:12PM -0700, Duane Powers wrote:
Hey, I've got a question, if you do the above, after the next cron
logrotate runs, and it touches new files, will they too be chown'd
to adm? Would that be in the logrotate.conf? (Perhaps I should look,
ok, no reference to
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 11 Apr 2001, Kenneth Vestergaard Schmidt wrote:
Having said that, is there any system loggin daemons which allow custom
facilities?
yes, syslog-ng, for example. This was one of the main reasons I had
switched to it in the past (and probably will again, when I have some time
to work
Hi.
The last couple of days I've been toying around with my logs, getting them
straightened up and such, and one thing struck me : logging in Debian is far
from efficient, let alone ideal.
My first grievance was, that my mail-logs quickly filled up with duplicate
information. Also, some of my
On Wed, 11 Apr 2001, Kenneth Vestergaard Schmidt wrote:
My first grievance was, that my mail-logs quickly filled up with duplicate
information. Also, some of my other log-files seemed to contain a lot of
duplicate entries. So, I started reading the syslog.conf manpage, and
actually got a
On Wednesday 11 April 2001 13:21, Giacomo Mulas wrote:
I want a good signal to noise ratio and I want to know exactly where I
should look to find a specific kind of log entry.
So a README to the new syslog.conf :)
If you have grand plans, I have a suggestion for you: prepare a set of
On Wed, 11 Apr 2001, Kenneth Vestergaard Schmidt wrote:
Having said that, is there any system loggin daemons which allow custom
facilities?
yes, syslog-ng, for example. This was one of the main reasons I had
switched to it in the past (and probably will again, when I have some time
to work on
Hi
On Wed, Apr 11, 2001 at 02:50:47PM +0200, Giacomo Mulas wrote:
It's probably the 3 people in total who bother to check the logs...
at least 4, just for the records, you can't administrate production servers
without having logcheck or similar installed!
For this reason (to stay on topic)
uOn Wed, Apr 11, 2001 at 02:50:47PM +0200, Giacomo Mulas wrote:
On Wed, 11 Apr 2001, Kenneth Vestergaard Schmidt wrote:
Having said that, is there any system loggin daemons which allow custom
facilities?
yes, syslog-ng, for example. This was one of the main reasons I had
switched to it
On Wednesday 11 April 2001 15:03, Christian Hammers wrote:
For this reason (to stay on topic) logging should at least keep the current
behaviour to have one log where everything is logged to, as it's now with
/var/log/syslog. And maybe the /var/log/auth.log with stuff that most
people may not
On Wed, Apr 11, 2001 at 03:29:16PM +0200, Kenneth Vestergaard Schmidt wrote:
Why? I think it is really wasted when everything is logged to syslog, and
also logged to other, more specific files. If you want to search for
Maybe people what to archive syslog for a year and the others only for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pedro;
If you go to http://www.sans.org/newlook/resources/IDFAQ/oddports.htm
You will find that port 4000 is a Trojan called Skydance and port
62459 is not listed. (I would suspect that it hasn't been added to the
list yet or perhaps the user of the
On Tue, Apr 10, 2001 at 08:08:02PM -0400, Doug Alcorn wrote:
ipchains -A output -i $ext_interface -p udp -s $your_ip_address
$unprivaleged_ports -d $nameserver_ip 53 -j ACCEPT
ipchains -A input -i $external_interface -p udp -s $nameserver_ip 53
-d $your_ip_address $unprivaleged_ports -j
Here is another one who bother to check the logs :)
Cheers,
Cristian
On Wed, 11 Apr 2001, JonesMB wrote:
Neato. That's 3 people in total who think it's a good idea.. :/
It's probably the 3 people in total who bother to check the logs...
make that 4. I always have an xterm with a tail -f
Tracking unstable.
Problems with OpenSSH.
OpenSSL version mismatch. Built against 90600f, you have 90601f
What package[s ] needs to be downgraded?
Thanks,
[EMAIL PROTECTED]
On Wed, Apr 11, 2001 at 02:50:45PM -0700 , [EMAIL PROTECTED] wrote:
Tracking unstable.
Problems with OpenSSH.
OpenSSL version mismatch. Built against 90600f, you have 90601f
What package[s ] needs to be downgraded?
libssl0.9.6 or recompile ssh
Petr Cech
On Wed, Apr 11, 2001 at 02:50:45PM -0700, [EMAIL PROTECTED] wrote:
OpenSSL version mismatch. Built against 90600f, you have 90601f
I fixed this problem by fetching the source packages for ssh and
building them locally ('apt-get source -b ssh').
noah, who still wishes the *open*ssh packages
I noticed this the other day. I compared two of my servers and found that
this combination works:
ii libssl0.9.60.9.6-2SSL shared libraries
ii ssh2.5.2p2-1 Secure rlogin/rsh/rcp replacement
(OpenSSH)
The latest libssl is 0.9.6a-1, which will give you the version
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Trying to build from source package, but this depends on gnome libs.
YUK
[EMAIL PROTECTED]
On Wed, Apr 11, 2001 at 06:17:53PM -0400, hpknight wrote:
I noticed this the other day. I compared two of my servers and found that
this
On Wed, Apr 11, 2001 at 04:15:59PM -0700, [EMAIL PROTECTED] wrote:
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Trying to build from source package, but this depends on gnome libs.
Yes, just edit debian/rules in the ssh source and remove the
'--with-gnome' or whatever it is from
My machine that got hammed with this needs the pam dev libs (obviously)
but there's a dependency problem with those right now in Sid, so I'm
waiting... (sigh).
On Wed, Apr 11, 2001 at 04:15:59PM -0700, [EMAIL PROTECTED] wrote:
Tried installing libssl0.9.6_0.9.6-2, no luck. Same errors.
Trying
Somebody mentioned on here that they always have an open terminal
running tail -f /var/log/syslog. I thought that I might try doing
this, but since /var/log/syslog is only readable by root, I decided to
try setting up sudo. I also want access to any log in /var/log. This
is what I have so far:
On Thu, Apr 12, 2001 at 12:38:10AM +, Adam Olsen wrote:
So my question: how do I set this up properly?
Not with sudo. ;)
chgrp adm /var/log/syslog # change group of file to adm
adduser (yourself) adm # put yourself into group adm
logout
log in again
:bam:
;D
On Thu, Apr 12, 2001 at 12:49:32AM +, Jim Breton wrote:
On Thu, Apr 12, 2001 at 12:38:10AM +, Adam Olsen wrote:
So my question: how do I set this up properly?
Not with sudo. ;)
chgrp adm /var/log/syslog # change group of file to adm
adduser (yourself) adm # put yourself into
On Wed, Apr 11, 2001 at 01:40:13PM -0500, JonesMB wrote:
make that 4. I always have an xterm with a tail -f /var/log/syslog running
so I can see what is happening to the system. I have a firewall setup but
I don't know if it is good enough so I usually monitor the syslog file for
suspicious
So my question: how do I set this up properly?
edit /etc/syslog.conf
add
*.*/dev/tty8
Kelly Steinmeyer
Linux Systems Administrator
Information Technology Services
Cameron University
Followup...
I was successfully able to fix the dependency problems with apt-get,
dselect was being too strict. Or apt-get was being too lenient... :)
On Wed, Apr 11, 2001 at 05:54:57PM -0600, Nate Duehr wrote:
My machine that got hammed with this needs the pam dev libs (obviously)
but there's
50 matches
Mail list logo
