Francesco, I read the original message over again and the obvious diagnosis is that somewhere on the host system, permissions are not properly set. Since the days of UNIX it has been proper to establish a wheel, which is a group user ID that owns processes and daemons, and that also has a very low ID with an invisible password. I cannot see whether you have established a password shadow file. I do not know whether your system is on a local area network. Are you running CVS? RCS? Subversion? Do you know how to lock and unlock files? Do you have root access, or at the least superuser privileges? Is sudo available to you? Do you have a sudoers file established? Are you familiar with /etc/passwd and /etc/shadow, respectively, as I believe they are called? I am not sure what your mean with references to /bin/true and /bin/false. Are you referring to files on your filesystem? I am at a terminal in a public library and can only go by memory. I do not know what system administrative techniques are available to you. The problem is not mission critical, it is a simple nuisance. It is contained entirely on the user end. It is not the Debian project's responsibility. I offered a suggestion on the spur of the moment without a Linux system available to me. I am a volunteer. I am encouraging you to find ways to contribute to the group project with solutions to your own problems. That is how all engineering projects are completed. How do I know? I am the original implementor of C++. I wrote *The C++ Programming Language* and *Accelerated C++*. I learned right alongside Bjarne Stroupstrop and published the first text under his name. I have a great deal of experience with solving computer-related problems without money or time. Design your own answers to problem as standard solutions or they will not be useful for anyone else. Start small, contribute often, and you will give a great deal. If you ask other people to solve all your problems, no one will.
Brendon, I am not just an elitist medical doctor, I am also an elitist medical director. If you "think a bug boils down" to something, you have not completed a diagnosis. As the original implementor of C++, I can tell you that the most important difference between C and C++ is that C++ always returns a value, most often 0, and that is why it is always faster. If a program returns 1 on exit, there has been an error in execution. This has been standard for almost 20 years. A cron script runs periodically. It is known as a periodic process. The classical UNIX System Adminstration text has been revised to cover Linux as well, and is endorsed by Linus Torvalds. Every edition of USAH/LSAH has a chapter on periodic processes, and cron is the workhorse. Anacron is a derivative. And you, amigo mio, have no idea what you are talking about. On 1/14/08, Brendon Higgins <[EMAIL PROTECTED]> wrote: > > Hi, > > It doesn't appear to be the case that the cron script is actually doing > any > updating by default. > > I think this bug boils down to this: The apt cron script conflicts with an > already running apt (or aptitude) process. If the user is running apt, > this > situation is not at all an error, the cron script just chose an > inconvenient > time to be run. If the default behaviour is for the cron script to run, > the > script should not just blindly report an error and exit 1, as the reports > that generates are confusing for users. (Sure made me wonder what the hell > was wrong.) > > And what kind of elitist garbage is it to then tell your legitimately > confused > users to go read a book and fix the problem-by-default themselves? > > That's my take on it. > > Peace, > Brendon > > Lord of, St. Luke Valor wrote (Sat, 12 Jan 2008): > > It only takes one hand to type. Fix it once, fix it for free, fix it for > > everyone, fix it forever. Have fun while you're at it. > > > > On 1/9/08, Francesco Poli <[EMAIL PROTECTED]> wrote: > > > On Tue, 8 Jan 2008 12:21:51 -0500 Lord of, St. Luke Valor wrote: > > > > I have a suggestion. > > > > > > > > 1) Find any text you are able on UNIX > > > > 2) Read about cron > > > > > > > > It is possible that cron was implemented in such a way that it must > be > > > > > > set > > > > > > > to task. If the Anacron message bothers you, I would remove APT from > > > > the cron process. It will free up memory. > > > > > > I *can* fix the issue for *my system*, but I would rather see the > > > *Debian package* fixed, so that other users will benefit from the > fix... > > > > > > After all, this is what the BTS is about: helping Debian to improve so > > > that users won't need to fix every single system by hand. Right? > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > >
