Auto update

[Jos Chrispijn]

Can someone tell me if there is a way of generating an email on the
moment that someone logs in to my FreeBSD server? The mail part
(phpmail) will be easy; I don't know yet how to trigger and pass
parameter to this script or redirect info to a file (that I then send by
email). Thanks.

Jos Chrispijn

[andrew clarke]

Post by Jos Chrispijn
Can someone tell me if there is a way of generating an email on the
moment that someone logs in to my FreeBSD server?

By which method? SSH?

[Jos Chrispijn]

Post by andrew clarke
By which method? SSH?

Yes, sorry I didn't mention that. If possible on both SSH and otherwise.

Thanks,
Jos

[Doug Hardie]

Can someone tell me if there is a way of generating an email on the moment that someone logs in to my FreeBSD server? The mail part (phpmail) will be easy; I don't know yet how to trigger and pass parameter to this script or redirect info to a file (that I then send by email). Thanks.

A cheesy way to do that is to use a popen ("tail -f /var/log/auth.log", "r") and then read that. It will give you every login regardless of ssh, telnet etc. You could then generate the emails from that. I have no idea just how resource intensive this might be. You would also have to ensure it got started by rc during boot._______________________________________________
freebsd-***@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-***@freebsd.org"

[Jos Chrispijn]

Post by Doug Hardie
A cheesy way to do that is to use a popen ("tail -f
/var/log/auth.log", "r") and then read that. It will give you every
login regardless of ssh, telnet etc. You could then generate the
emails from that. I have no idea just how resource intensive this
might be. You would also have to ensure it got started by rc during
boot._______________________________________________

In order to find out if someone logged in, I should then first copy
auth.log to auth2.log, and do a compare and then do the tail trick. Have
to cron that every half a minute.
I would like to know if there is something that is alterted on the
moment that someone logs on thus forcing evt. your tail suggestion

thanks,
Jos Chrispijnj

[Ed Jobs]

Post by Jos Chrispijn
In order to find out if someone logged in, I should then first copy
auth.log to auth2.log, and do a compare and then do the tail trick. Have
to cron that every half a minute.
I would like to know if there is something that is alterted on the
moment that someone logs on thus forcing evt. your tail suggestion
thanks,
Jos Chrispijnj

you could try using syslog to do that. check the man page of syslog.conf, and
search for "auth." you could then populate a file with the successful logins
as they happen

[RW]

On Sun, 11 Apr 2010 11:32:27 +0200

Post by Jos Chrispijn

Post by Doug Hardie
A cheesy way to do that is to use a popen ("tail -f
/var/log/auth.log", "r") and then read that. It will give you every
login regardless of ssh, telnet etc. You could then generate the
emails from that. I have no idea just how resource intensive this
might be. You would also have to ensure it got started by rc during
boot._______________________________________________

In order to find out if someone logged in, I should then first copy
auth.log to auth2.log, and do a compare and then do the tail trick.
Have to cron that every half a minute.
I would like to know if there is something that is alterted on the
moment that someone logs on thus forcing evt. your tail suggestion

tail -f *is* event driven. When a new line is appended to auth.log,
tail will output it.

You should probably use

$ tail -F -n 0 /var/log/auth.log

[krad]

Post by RW
$ tail -F -n 0 /var/log/auth.log

Definitely use the -F rather than -f option as it will handle log rotation

[Randal L. Schwartz]

Jos> In order to find out if someone logged in, I should then first copy auth.log
Jos> to auth2.log, and do a compare and then do the tail trick. Have to cron that
Jos> every half a minute.

No, just track it with tail -f as was already suggested.

tail -f /var/log/authlog | while read aline; do; ... ; done

The code in the middle will get executed as each line appears in the
file. This even survives authlog renaming when you logroll.

[krad]

Post by Randal L. Schwartz
Jos> In order to find out if someone logged in, I should then first copy auth.log
Jos> to auth2.log, and do a compare and then do the tail trick. Have to cron that
Jos> every half a minute.
No, just track it with tail -f as was already suggested.
tail -f /var/log/authlog | while read aline; do; ... ; done
The code in the middle will get executed as each line appears in the
file. This even survives authlog renaming when you logroll.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - [phone]
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "

no use -F not -f as log rotation will break it otherwise

[krad]

Post by Jos Chrispijn
Can someone tell me if there is a way of generating an email on the

moment that someone logs in to my FreeBSD server? The mail part (phpmail)
will be easy; I don't know yet how to trigger and pass parameter to this
script or redirect info to a file (that I then send by email). Thanks.
A cheesy way to do that is to use a popen ("tail -f /var/log/auth.log",
"r") and then read that. It will give you every login regardless of ssh,
telnet etc. You could then generate the emails from that. I have no idea
just how resource intensive this might be. You would also have to ensure it
got started by rc during boot._________________________

It shouldn't be to bad as I use that method to generate stats from log files
for snmp. The log files I tail have about 200 odd lines per second and the
boxes handle it fine. But they are decentish spec but not extravagant (dell
2850 with 4gig ram)