Difference between revisions of "Equipment/Babbage/LogBook"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | ===27/4/2011 [[User:Artag|Artag]] === | ||
| + | |||
| + | There were two tftp servers running, or attempting to run. Between them they were using about 50% of the CPU writing messages such as | ||
| + | |||
| + | Apr 27 20:31:40 babbage atftpd[1610]: bind: Cannot assign requested address | ||
| + | Apr 27 20:31:40 babbage atftpd[1610]: recvmsg: Socket operation on non-socket | ||
| + | Apr 27 20:31:40 babbage atftpd[1610]: bind: Cannot assign requested address | ||
| + | Apr 27 20:31:40 babbage atftpd[1610]: recvmsg: Socket operation on non-socket | ||
| + | |||
| + | There seems to be no need for either at the moment, so I disabled tftpd manually in /etc/inetd.conf, and disabled aftpdfd with 'update-rc.d -n atftpd disable' | ||
| + | |||
| + | If you need one running, please choose one or the other... | ||
| + | |||
| + | |||
===25/2/2011 Note by [[User:Ciemon|Ciemon]] === | ===25/2/2011 Note by [[User:Ciemon|Ciemon]] === | ||
Revision as of 19:57, 27 April 2011
27/4/2011 Artag
There were two tftp servers running, or attempting to run. Between them they were using about 50% of the CPU writing messages such as
Apr 27 20:31:40 babbage atftpd[1610]: bind: Cannot assign requested address Apr 27 20:31:40 babbage atftpd[1610]: recvmsg: Socket operation on non-socket Apr 27 20:31:40 babbage atftpd[1610]: bind: Cannot assign requested address Apr 27 20:31:40 babbage atftpd[1610]: recvmsg: Socket operation on non-socket
There seems to be no need for either at the moment, so I disabled tftpd manually in /etc/inetd.conf, and disabled aftpdfd with 'update-rc.d -n atftpd disable'
If you need one running, please choose one or the other...
25/2/2011 Note by Ciemon
5 packages can be updated. 4 updates are security updates.
The following packages will be upgraded:
linux-headers-2.6.31-22 linux-headers-2.6.31-22-generic linux-image-2.6.31-22-generic linux-libc-dev tzdata
The kernel upgrades will need a reboot after the upgrade, so upgrade aborted for now until the reboot procedure is defined.
- The upgrade procedure is currently DON'T unless it's absolutely necessary, and you've checked with people it affects (especially IRC).
- The reboot procedure is DON'T unless it's already completely broken. Ms7821 00:55, 26 February 2011 (UTC)