Overflow on /dev/null, please empty the bit bucket.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Overflow on /dev/null, please empty the bit bucket.
Hi, I get this error Overflow on /dev/null, please empty the bit bucket. when i open an shell, it give me this message before the prompt line. I don't know where is that bit bucket stuff, I search in google but all the explanation I see didn't help to my problem, any ideas?????
Thats a joke. Their is no bit bucket. Unix tools are scattered with these types of in jokes. Think about a noob at some workshop being sent for a left-handed screwdriver.
Your actual problem probably something else is going wrong. That tool doesn't know whats happening, So its giving you this message in jest. Emacs does this.
An Joke??? I thought it was serious Maybe because sometimes in KDE I get and error that says CPU Overloaded, I get this message constantly and i thought that the 'Joke' was maybe because of the message cpu overloaded, and if bit bucket doesn't exist but /dev/null do? I mean before I do have a problem whit alsa too, but i resolve it, the error message that alsa give me those days was, can't locate device /dev/sdp or something like that, using instead /dev/null so do I have to believe slackware is full of Joke???
No /dev/null is a real thing. ( Thats not a joke ) Its a null device, Its so you can redirect output. Anything directed to /dev/null is simply ignored/destroyed. Think of it as a little black hole.
When the system couldn't get ALSA working, it has to direct the output to somewhere since it couldn't find /dev/dsp So it redirects it too /dev/null.
CPU overloaded? I've never heard of that.
This message means their is a problem somwhere, Its probably in bash, or something. Maybe theirs an error in your .bashrc file as its coming up just before the prompt in your shell.
Maybe something is being directed too /dev/null but for some reason this is failing, so its giving you this message. Is their a program name with this message?
Ok little bucket doesn't exist? but the message CPU overloaded in /dev/null yes, I don't know what apps or what program is causing that. because the error message doesn't point to one it just say CPU Overload and an option that says Ok, so i give the Ok option and my box still working normal. I'm getting this error since i upgrade my kernel, 2.4.23 to 2.4.24 it's not all day i received this message 1 time in a week and only in KDE, not in other window manager maybe it's arts or something of alsa who knows, I haven't worried about it yet, but i thought the overflow stuff was talking about the CPU Overloaded.
Overflows happen when something is sent moreinformation than it can handle at once. /dev/null can handle an infinite amount ( cuz its destroying it ) you can't overflow a blackhole. normal devices can have overflow problems because theirs only so much stuff that can do at once.
Oh, hahaha so i guess i was a little idiot whit the overflow to /dev/null
and maybe the error messages from CPU overloaded is something that points to /dev/null too because after that message my box still working normal. Well i think that arts is giving that error, but my sound still work fine i don't know if slacky if using alsa from arts or alsa OSS (or they bot are the same ) for my sound, but my sound still working even if the error message appears. maybe it's something i have to not worry about,
Yes i have read in google something about the fortune stuff, but it says chek profile and the part that mention fortune comment it or delete it I go to profile and don't see any fortune stuff but i do what Tinkster told me and yes i got something call fortune:
marian@Slackware:~$ fortune -m "/dev/null"
%% (fortunes)
Overflow on /dev/null, please empty the bit bucket.
why this happen??? how that cookie or i don't know call fortune get to my box? where i have to go to delete it.
Yes i have read in google something about the fortune stuff, but it says check profile and the part that mention fortune comment it or delete it I go to profile and don't see any fortune stuff but i do what Tinkster told me and yes i got something call fortune:
marian@Slackware:~$ fortune -m "/dev/null"
%% (fortunes)
Overflow on /dev/null, please empty the bit bucket.
why this happen??? how that cookie or i don't know call fortune get to my box? where i have to go to delete it.
I still haven't see the coolest of that 'Joke' because I haven't see that message before never, so why this fortune stuff exist now. I'm still don't get it. By the way I am she not him.
You may have a program that is using all of your resources.
From a shell, type 'top' and look to see if there is a process that is running at above 95% all of the time.
If there is, that is most likely the problem.
If the process is somthing that you are not using, from a shell type 'kill (pid)' pid is the process ID number. Example: kill 2398
You can deal with that process or post the results for help on stopping it.
Originally posted by little_ball
I still haven't see the coolest of that 'Joke'
because I haven't see that message before never,
so why this fortune stuff exist now. I'm still don't get it.
Look, fortune is a little program that generates
random quotes ... in slack, it's by default run
in any login-shell ... that is, if you changed your
.bashrc or .bash_login behaviour recently, that's
why you get it now ... if you don't like it, do as I
said above! :)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.