?

Log in

No account? Create an account
Linux Community's Journal
 
[Most Recent Entries] [Calendar View] [Friends View]

Tuesday, May 11th, 2004

Time Event
12:57p
ok, I got paranoid.
I'm recompiling my kernel for the first time.

Here's what I'm doing:

cd /usr/src/[kernelver]
make xconfig
{blah blah blah}
make bzImage && make modules modules_install
make install


so will that put the new copy of the kernel in my /boot dir? will it write over my current one since it's already there?


*edit*
it put it in as and left everything as it was. it even did my grub config, although it didn't set it to the default kernel.
go go fedora core2!
2:47p
Bandwidth monitor app for linux?
Hi everybody,

Bandwidth is costly where I live, and "broadband" home connections
start at 64/128 kbps and have monthly caps like 500MB. For people
who face such constraints it would be useful to have a breakdown
of their bandwidth utilization app-wise so that they can modify
their 'net usage habits accordingly.

I looked around to see if such an app exists, but while there are
a zillion bandwidth monitor apps for *nix they are aimed at
sysadmins and don't show app-wise breakdowns. Also, most show
only real time data and not consolidated graphs over a time period.
I found a (proprietary) software called netlimiter for
Windows that does roughly what I was looking for.

If there isn't anything for linux I would like to write one.

The design of this hypothetical app for linux would be like this:
* The backend would be a daemon coupled with a kernel module that
would intercept TCP send/recv calls and log them. The data logged
would be name of the executable, user, and size of packet. The
daemon would listen on some port and pass this data on to clients
(there should be some security rules to specify which clients are
allowed to connect.) The backend should also offer a way to throttle
bandwidth in an app-wise manner. If the limit is exceeded the packet
should be dropped. The challenge is to do all this without greatly
impacting performance.

* The frontend collects this data and presents it in various pretty
ways to the user. Some examples:
-- Show real time bandwidth usage graphs, app wise, user wise and
machine wise, both incoming and outgoing.
-- Show aggregate graphs ala webalizer, again app wise, user wise
and machine wise.
-- Allow throttling and bandwidth quotas.
etc. Of course, multiple frontends can exist.

Any thoughts/criticisms/suggestions? Anyone want to join me?
9:39p
Anyone wanna show off?
I've taken up shell scripting as a hobby, and figured some of my scripts might be useful to someone so I made a sourceforge project to hold it. I'm about ready to upload the first release, but I'd like someone more experienced to look it over first. Everything works, the code is just "sloppy" due to my inexperience. Anyone here willing to do a read-through and some tweaks before I send it off?

<< Previous Day 2004/05/11
[Calendar]
Next Day >>
About LiveJournal.com