Probably a stupid question, but how much space do i need in my account to install and run my eggdrop?
I have 10MB at the moment and I got as far as the "make install DEST=/home/name/botdir" stage with no problems, but now i am out of space... I removed the install archive (which wasnt much) and I have roughly 2 megs free. Are there any files i can delete at this stage to free up enough space to carry on?
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
space in shell
In sitiuations where a full compile and install can't be done, you find that the shell provider, has allreadynprovided you will pre-compiled binaries.
I sugest you read all the shell providers notes, FAQ's and T&C's to find out if the shell is allowed eggdrop, and if they provide pre-compiled binaries. You may find they only allow there own if the do provide them as weel, for security reasons.
From memory, there is nothing your can delete, other than the tarball you downloaded, before the "make install" stage. As the install phase will complain of missing files and stop otherwise.
You can run the eggdrop from the directory you compiled in, though you may find some language files need moving to the right directory, and that you need to change the modules directory in the config file.
Otherwise, I would see the shell provider about a temporary increase, so that you may install correctly.
I sugest you read all the shell providers notes, FAQ's and T&C's to find out if the shell is allowed eggdrop, and if they provide pre-compiled binaries. You may find they only allow there own if the do provide them as weel, for security reasons.
From memory, there is nothing your can delete, other than the tarball you downloaded, before the "make install" stage. As the install phase will complain of missing files and stop otherwise.
You can run the eggdrop from the directory you compiled in, though you may find some language files need moving to the right directory, and that you need to change the modules directory in the config file.
Otherwise, I would see the shell provider about a temporary increase, so that you may install correctly.
I had that problem with 1.6.10 on a shell with 10 MB and 1 MB grace limit.
I removed all the files I didnt need, unpacked the archive, removed the archive and than configured and compiled the bot with just the modules I really need. It worked fine. With the 1.6.12 I had less trouble, with the same procedure I didn't even get any warning. So 10 MB should be enough, even if it can be a bit difficult.
I removed all the files I didnt need, unpacked the archive, removed the archive and than configured and compiled the bot with just the modules I really need. It worked fine. With the 1.6.12 I had less trouble, with the same procedure I didn't even get any warning. So 10 MB should be enough, even if it can be a bit difficult.
-
DDenisF
I got a 20 meg shell on a freebsd5 machine,
i download the tar of the latest CVS snapshot, untar it, delete the tar.gz, cd eggdrop1.6.
at that stage i have 5 megs used.
then i do configure and make config, have 10 left, when i start make and it goes till share.so linking, then stops cuz i run out of space.
how can i fix this ?? (can't possibly be that a fresh eggdrop takes 20 meg)
i download the tar of the latest CVS snapshot, untar it, delete the tar.gz, cd eggdrop1.6.
at that stage i have 5 megs used.
then i do configure and make config, have 10 left, when i start make and it goes till share.so linking, then stops cuz i run out of space.
how can i fix this ?? (can't possibly be that a fresh eggdrop takes 20 meg)
The simple answer is don't use CVS code. It's designed for developers and beta testers, and not for "joe user".
The CVS version is setup in a way, that it compiles with memory debugging code enabled.
This is turned off when a release is published (but can be enabled at any time).
ALterntivly, use "make eggdrop" rather than just "make"
The CVS version is setup in a way, that it compiles with memory debugging code enabled.
This is turned off when a release is published (but can be enabled at any time).
ALterntivly, use "make eggdrop" rather than just "make"