Stable
This shows that after the last reboot (when the new memory was installed) the load on CPU, process slots and memory has stablelized:
So it’s only memory usage that increased up to the current level and doesn’t change very much – just a spike that is consistent with the extra processes, and so is paging: New processes require memory and of course, this must be acquired and distributed – hence tis paging.
These spikes in number of processes. memory usage and paging occur between 6:45 and 7:00, and between 18:45 and 19:00, every day. You might expect (as I did :)) that there is a batch job that runs at these moments, but $SHO QUE
shows none:
$ sho que
Batch queue BACKUP, idle, on DIANA::
Printer queue DCPS_QUEUE, idle, on DIANA::"IP_RawTCP/192.168.0.251:9100",
mounted form DCPS$DEFAULT (stock=DEFAULT)
Printer queue HPTN2100, stopped, on DIANA::"192.168.0.251:9100",
mounted form DEFAULT
Batch queue NORMAL, idle, on DIANA::
Generic batch queue SYS$BATCH
Entry Jobname Username Status
----- ------- -------- ------
218 PreciseMail Stats
SYSTEM Holding until 9-SEP-2015 15:05:00
207 PreciseMail Notify
SYSTEM Holding until 9-SEP-2015 15:30:00
190 reset_syslog SYSTEM Holding until 10-SEP-2015 00:00:00
191 scan_log SYSTEM Holding until 10-SEP-2015 00:00:00
192 do_backup SYSTEM Holding until 10-SEP-2015 00:00:00
195 PreciseMail Nightly
SYSTEM Holding until 10-SEP-2015 00:05:00
200 PreciseMail AutoUpdate
SYSTEM Holding until 10-SEP-2015 02:00:00
810 save_logs SYSTEM Holding until 1-OCT-2015 01:00:00
Generic printer queue SYS$PRINT
Batch queue SYS$START, stopped, on DIANA::
Batch queue T4$BATCH, available, on DIANA::
Entry Jobname Username Status
----- ------- -------- ------
143 T4$COLLECT SYSTEM Executing
189 T4$COLLECT SYSTEM Holding until 9-SEP-2015 23:59:00
Generic server queue TCPIP$SMTP
Generic server queue TCPIP$SMTP_DIANA_00
Server queue TCPIP$SMTP_DIANA_01, stopped, on DIANA::, mounted form DEFAULT
Server queue TCPIP$SMTP_DIANA_1, idle, on DIANA::, mounted form DEFAULT
So now it is a matter of looking for logfiles created on these moments; perhaps $ ACC
or $ ANA/AUDIT
will show something 🙂
Track images moved
The images of all our trips, tracks and travels now take about 10 Gb – almost the full size of the logical disk that contains all of the web data. Adding another 1 Gb (or more) of the Lahn Wanderweg (walked in 2014), now (almost) ready for publication, would not fit. So I added another 32Gb disk to the system, initialized it and mover all the images to that physical disk. I could of course have created a logical disk of sufficient size (say 20Gb) which is, indeed, easier to move, and backup (just a single file); but I can do so on the current disk, once the files have been removed, the original logical disk could be used as well; just adding the other files to this drive as well – bit by bit – and re-create the disk-containers on that disk once more – in the appropriate size.
This move however gives me time and space to maneuver.
Another addition: Images and videos of Tessa – our Little Black Devil. Video won’t show fluently at the moment because the disk is heavily loaded (because backup of the track-images).