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 XFREE86
reboot
reboot(1M)reboot(1M)NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)