How to make a script that logs bandwidth on a specific port?
I have a script that runs right before a daily reboot that captures the amount of MB transmitted up and pulled down since last reboot.
In looking at the raw output of /proc/net/dev, I know that this particular script will only yield the info on a Ethernet device. Is there any way to write a script that does something like this per port? I'd like to know, how much bandwidth is being consumed by the web pages being hosted on port 80 vs. the Minecraft server being hosted on port 25565.
I have to write a shell script like this--
1) Utility will be run under the directory owner.
2) This utility will clean files in ABC/logs. And following logs will be backed up or deleted.
Dispatcher Logs
Middle tier Logs
Sage log
Sage monitor log
Sage db clean up result log
Core files ... (12 Replies)
In general for intalling a package like we do
./configure, make , make install
But if we want to integrate the package with a huge source base
what are the things to be taken care
could some one have a light on purpose of ./configure , make and make install
along with above question.
I... (1 Reply)
I need to extract data from logs for a mentioned date range..Its quite urgent can anyone help me out with it..its to be written in unix..just thought its better to specify.. (4 Replies)
Hi,
I've been looking for a few hours now, reading various docs and man pages, but the info I found so far is either not what I was looking for or I just don't get how to do the thing I need....
So, my "problems" is that I have a server running on a specific port and I need to shape traffic... (2 Replies)
Hi, I would like to write a shell script that will:
-search the files of a specific user to find any audio files with a bandwidth iqual or greater than 192 kps
- on the results i should see the file name along with all the whole file route and each file's size
So I guess i should be using... (1 Reply)
i have a log file that has the date and time that looks like this:
Wed Jun 28 15:46:21 2012 test failed tailed passed passed not error panic
what we want to focus on is the first 5 columns because they contain the date and time.
the date and time can be anywhere on the line. in this... (6 Replies)
Assuming i have /usr/local/psa/var/log/mail.log on client server.
What are the configuration on rsyslog (server) and rsyslog (client)?
on rsyslog (server) i would also want it to be put on a separate log file for example: /var/log/client-server-hostname01/mail.log ,... (2 Replies)
Hello again people,
I currently searching for a code/script that will allow it to check if a specific port is open, lets say 123. Found a public script on a ftp but I dont know how and what to modify in it to suit my needs. (I think this is a evil code and I want to use it as an example).
... (3 Replies)
Appreciate help for the below issue.
Im using below code.....I dont want to attach the logs when I ran the perl twice...I just want to take backup with today date and generate new logs...What I need to do for the below scirpt..............
1)if logs exist it should move the logs with extention... (1 Reply)
Discussion started by: Sanjeev G
1 Replies
LEARN ABOUT MOJAVE
lastlog
UTMP(5) BSD File Formats Manual UTMP(5)NAME
utmp, wtmp, lastlog -- login records (DEPRECATED)
SYNOPSIS
#include <utmp.h>
DESCRIPTION
The interfaces in file <utmp.h> are all DEPRECATED and are only provided for compatibility with previous releases of Mac OS X. See
pututxline(3) and utmpx(5) for the supported interfaces.
<utmp.h> declares the structures used to record information about current users in the file utmp, logins and logouts in the file wtmp, and
last logins in the file lastlog. The time stamps of date changes, shutdowns and reboots are also logged in the wtmp file.
These files can grow rapidly on busy systems, daily or weekly rotation is recommended. If any of these files do not exist, it is not cre-
ated. These files must be created manually and are normally maintained in either the script /etc/daily or the script /etc/weekly. (See
cron(8).)
#define _PATH_UTMP "/var/run/utmp"
#define _PATH_WTMP "/var/log/wtmp"
#define _PATH_LASTLOG "/var/log/lastlog"
#define UT_NAMESIZE 8
#define UT_LINESIZE 8
#define UT_HOSTSIZE 16
struct lastlog {
time_t ll_time;
char ll_line[UT_LINESIZE];
char ll_host[UT_HOSTSIZE];
};
struct utmp {
char ut_line[UT_LINESIZE];
char ut_name[UT_NAMESIZE];
char ut_host[UT_HOSTSIZE];
time_t ut_time;
};
Each time a user logs in, the login program looks up the user's UID in the file lastlog. If it is found, the timestamp of the last time the
user logged in, the terminal line and the hostname are written to the standard output. (Providing the login is not quiet, see login(1).) The
login program then records the new login time in the file lastlog.
After the new lastlog record is written , the file utmp is opened and the utmp record for the user inserted. This record remains there until
the user logs out at which time it is deleted. The utmp file is used by the programs rwho(1), users(1), w(1), and who(1).
Next, the login program opens the file wtmp, and appends the user's utmp record. The same utmp record, with an updated time stamp is later
appended to the file when the user logs out. (See launchd(8).) The wtmp file is used by the programs last(1) and ac(8).
In the event of a date change, a shutdown or reboot, the following items are logged in the wtmp file.
reboot
shutdown A system reboot or shutdown has been initiated. The character '~' is placed in the field ut_line, and reboot or shutdown in the
field ut_name. (See shutdown(8) and reboot(8).)
date The system time has been manually or automatically updated. (See date(1).) The command name date is recorded in the field
ut_name. In the field ut_line, the character '|' indicates the time prior to the change, and the character '{' indicates the new
time.
FILES
(These files no longer exist in 10.5 or later.)
/var/run/utmp The utmp file.
/var/log/wtmp The wtmp file.
/var/log/lastlog The lastlog file.
SEE ALSO last(1), login(1), who(1), ac(8), launchd(8)HISTORY
A utmp and wtmp file format appeared in Version 6 AT&T UNIX. The lastlog file format appeared in 3.0BSD.
4th Berkeley Distribution March 17, 1994 4th Berkeley Distribution