December 3, 201411 yr This is sort of a pet peeve of mine as I'm writing a badblocks drive stress/clear/health tool that can be spawned from the webGui and run in the background. When using the syslog monitor from the front end/bar, syslog is not presented in a monospaced font. It should probably be presented that way to preserve spacing for cut/paste and quick review. I would do it myself with a patch, only I'm not sure where to change it. here's an example of a screen dump via console. Dec 3 01:03:32 unRAIDb badblocks[4359]: DEVICE /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 3 01:03:32 unRAIDb badblocks[4359]: 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 81 Dec 3 01:03:32 unRAIDb badblocks[4359]: 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 499 Dec 3 01:03:32 unRAIDb badblocks[4359]: 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 7 Dec 3 01:03:32 unRAIDb badblocks[4359]: 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 Dec 3 01:03:32 unRAIDb badblocks[4359]: 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 24 Dec 3 01:03:32 unRAIDb badblocks[4359]: 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6 Dec 3 01:03:32 unRAIDb badblocks[4359]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 25/43) Dec 3 01:03:32 unRAIDb badblocks[4359]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: Dec 3 01:03:32 unRAIDb badblocks[4359]: Checking for bad blocks in read-write mode Dec 3 01:03:32 unRAIDb badblocks[4359]: From block 0 to 3907018583 Dec 3 01:03:32 unRAIDb badblocks[4359]: Testing with pattern 0x00: 0.00% done, 0:00 elapsed. (0/0/0 errors) Dec 3 01:04:32 unRAIDb badblocks[4359]: 0.24% done, 1:00 elapsed. (0/0/0 errors) Dec 3 01:05:32 unRAIDb badblocks[4359]: 0.47% done, 2:00 elapsed. (0/0/0 errors) Dec 3 01:06:32 unRAIDb badblocks[4359]: 0.70% done, 3:00 elapsed. (0/0/0 errors) Dec 3 01:07:32 unRAIDb badblocks[4359]: 0.94% done, 4:00 elapsed. (0/0/0 errors) Dec 3 01:08:32 unRAIDb badblocks[4359]: 1.18% done, 5:00 elapsed. (0/0/0 errors) Dec 3 01:09:32 unRAIDb badblocks[4359]: 1.41% done, 6:00 elapsed. (0/0/0 errors) Dec 3 01:10:32 unRAIDb badblocks[4359]: 1.65% done, 7:00 elapsed. (0/0/0 errors) Dec 3 01:11:32 unRAIDb badblocks[4359]: 1.88% done, 8:00 elapsed. (0/0/0 errors) Dec 3 01:12:32 unRAIDb badblocks[4359]: 2.12% done, 9:00 elapsed. (0/0/0 errors) and via the syslog view. Dec 3 00:38:42 unRAIDb kernel: ata2: EH complete Dec 3 01:03:32 unRAIDb badblocks[4359]: START Wed Dec 3 01:03:32 EST 2014 (0) /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: DEVICE /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 3 01:03:32 unRAIDb badblocks[4359]: 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 81 Dec 3 01:03:32 unRAIDb badblocks[4359]: 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 499 Dec 3 01:03:32 unRAIDb badblocks[4359]: 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 7 Dec 3 01:03:32 unRAIDb badblocks[4359]: 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 Dec 3 01:03:32 unRAIDb badblocks[4359]: 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 24 Dec 3 01:03:32 unRAIDb badblocks[4359]: 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6 Dec 3 01:03:32 unRAIDb badblocks[4359]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 25/43) Dec 3 01:03:32 unRAIDb badblocks[4359]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: Dec 3 01:03:32 unRAIDb badblocks[4359]: Checking for bad blocks in read-write mode Dec 3 01:03:32 unRAIDb badblocks[4359]: From block 0 to 3907018583 Dec 3 01:03:32 unRAIDb badblocks[4359]: Testing with pattern 0x00: 0.00% done, 0:00 elapsed. (0/0/0 errors) Dec 3 01:04:32 unRAIDb badblocks[4359]: 0.24% done, 1:00 elapsed. (0/0/0 errors) Dec 3 01:05:32 unRAIDb badblocks[4359]: 0.47% done, 2:00 elapsed. (0/0/0 errors) Dec 3 01:06:32 unRAIDb badblocks[4359]: 0.70% done, 3:00 elapsed. (0/0/0 errors)
December 3, 201411 yr Author I totally agree! On the plus side, in the tools -> syslog view, there is now a [download] button. I've been wondering if it would make sense to make the file preserved in this .zip archive as syslog.txt with cr/lf end of lines. I.E. to make it quicker to download and view the file for assistance.
December 3, 201411 yr Experienced users don't need it, we always use tools that are Linux aware. Mac users won't care either. While we could do things like this that make it easier for new users, and try to remember to add the fromdos/todos confusion here and there, I strongly subscribe to the view that new Windows users should learn early that this is Linux, and learn a few adaptations that will help them in the long run. Teach them early something like this: While great effort has been put into making UnRAID easy to use for Windows users, an UnRAID server is a Linux server, and Linux does a few things differently. Line endings is one of them. 1. Do not use Windows Notepad with UnRAID files, use tools that are Linux aware and can handle the Linux line endings (eg. NotePad++, NotePad2, PSPad, etc). 2. With only a few exceptions (such as the 'go' file), text files saved to an UnRAID server need to have Linux line endings.
December 3, 201411 yr Author I can say that I tend to avoid bothering with syslog files if they are unix LF delimited when posted on the forum. I have to open the zip, then cut and paste the log somewhere, Navigate, then right click to open with editpad/notepad++ After I review it, I have to now navigate and delete 2 files. If it was a dos .txt file in the .zip archive, I would just click it and be done. I don't feel all that strongly about this, I'll avoid the ones I don't want to deal with.
December 11, 201411 yr This is sort of a pet peeve of mine as I'm writing a badblocks drive stress/clear/health tool that can be spawned from the webGui and run in the background. When using the syslog monitor from the front end/bar, syslog is not presented in a monospaced font. It should probably be presented that way to preserve spacing for cut/paste and quick review. I would do it myself with a patch, only I'm not sure where to change it. here's an example of a screen dump via console. Dec 3 01:03:32 unRAIDb badblocks[4359]: DEVICE /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 3 01:03:32 unRAIDb badblocks[4359]: 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 81 Dec 3 01:03:32 unRAIDb badblocks[4359]: 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 499 Dec 3 01:03:32 unRAIDb badblocks[4359]: 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 7 Dec 3 01:03:32 unRAIDb badblocks[4359]: 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 Dec 3 01:03:32 unRAIDb badblocks[4359]: 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 24 Dec 3 01:03:32 unRAIDb badblocks[4359]: 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6 Dec 3 01:03:32 unRAIDb badblocks[4359]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 25/43) Dec 3 01:03:32 unRAIDb badblocks[4359]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: Dec 3 01:03:32 unRAIDb badblocks[4359]: Checking for bad blocks in read-write mode Dec 3 01:03:32 unRAIDb badblocks[4359]: From block 0 to 3907018583 Dec 3 01:03:32 unRAIDb badblocks[4359]: Testing with pattern 0x00: 0.00% done, 0:00 elapsed. (0/0/0 errors) Dec 3 01:04:32 unRAIDb badblocks[4359]: 0.24% done, 1:00 elapsed. (0/0/0 errors) Dec 3 01:05:32 unRAIDb badblocks[4359]: 0.47% done, 2:00 elapsed. (0/0/0 errors) Dec 3 01:06:32 unRAIDb badblocks[4359]: 0.70% done, 3:00 elapsed. (0/0/0 errors) Dec 3 01:07:32 unRAIDb badblocks[4359]: 0.94% done, 4:00 elapsed. (0/0/0 errors) Dec 3 01:08:32 unRAIDb badblocks[4359]: 1.18% done, 5:00 elapsed. (0/0/0 errors) Dec 3 01:09:32 unRAIDb badblocks[4359]: 1.41% done, 6:00 elapsed. (0/0/0 errors) Dec 3 01:10:32 unRAIDb badblocks[4359]: 1.65% done, 7:00 elapsed. (0/0/0 errors) Dec 3 01:11:32 unRAIDb badblocks[4359]: 1.88% done, 8:00 elapsed. (0/0/0 errors) Dec 3 01:12:32 unRAIDb badblocks[4359]: 2.12% done, 9:00 elapsed. (0/0/0 errors) and via the syslog view. Dec 3 00:38:42 unRAIDb kernel: ata2: EH complete Dec 3 01:03:32 unRAIDb badblocks[4359]: START Wed Dec 3 01:03:32 EST 2014 (0) /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: DEVICE /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB Dec 3 01:03:32 unRAIDb badblocks[4359]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 3 01:03:32 unRAIDb badblocks[4359]: 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 81 Dec 3 01:03:32 unRAIDb badblocks[4359]: 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 499 Dec 3 01:03:32 unRAIDb badblocks[4359]: 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 7 Dec 3 01:03:32 unRAIDb badblocks[4359]: 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 Dec 3 01:03:32 unRAIDb badblocks[4359]: 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 24 Dec 3 01:03:32 unRAIDb badblocks[4359]: 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6 Dec 3 01:03:32 unRAIDb badblocks[4359]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8 Dec 3 01:03:32 unRAIDb badblocks[4359]: 194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 25/43) Dec 3 01:03:32 unRAIDb badblocks[4359]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 Dec 3 01:03:32 unRAIDb badblocks[4359]: Dec 3 01:03:32 unRAIDb badblocks[4359]: Checking for bad blocks in read-write mode Dec 3 01:03:32 unRAIDb badblocks[4359]: From block 0 to 3907018583 Dec 3 01:03:32 unRAIDb badblocks[4359]: Testing with pattern 0x00: 0.00% done, 0:00 elapsed. (0/0/0 errors) Dec 3 01:04:32 unRAIDb badblocks[4359]: 0.24% done, 1:00 elapsed. (0/0/0 errors) Dec 3 01:05:32 unRAIDb badblocks[4359]: 0.47% done, 2:00 elapsed. (0/0/0 errors) Dec 3 01:06:32 unRAIDb badblocks[4359]: 0.70% done, 3:00 elapsed. (0/0/0 errors) I'm actually going to move this thread to the roadmap forum. I wouldn't call this as much of a defect as a feature request. Nothing isn't working as intended, but maybe we should change our intentions ;-).
December 11, 201411 yr Author I'm actually going to move this thread to the roadmap forum. I wouldn't call this as much of a defect as a feature request. Nothing isn't working as intended, but maybe we should change our intentions ;-). As long as it gets fixed. Seeing it as it would be seen on a console with proper alignment goes a long way towards rapid review.
December 12, 201411 yr I've been wondering if it would make sense to make the file preserved in this .zip archive as syslog.txt with cr/lf end of lines. I.E. to make it quicker to download and view the file for assistance. I'm not sure how this would "make it quicker"? Adding extra bytes would slow it down, surely? ... not that the difference would be detectable.
December 12, 201411 yr I've been wondering if it would make sense to make the file preserved in this .zip archive as syslog.txt with cr/lf end of lines. I.E. to make it quicker to download and view the file for assistance. I'm not sure how this would "make it quicker"? Adding extra bytes would slow it down, surely? ... not that the difference would be detectable. It would make it "quicker" for the user to view from any Windows OS as they wouldn't have to find a program that can handle Unix Linefeeds. As for zipping it, that should compress down to under 30% of the original size. Text compresses amazingly well.
December 12, 201411 yr Author I've been wondering if it would make sense to make the file preserved in this .zip archive as syslog.txt with cr/lf end of lines. I.E. to make it quicker to download and view the file for assistance. I'm not sure how this would "make it quicker"? Adding extra bytes would slow it down, surely? ... not that the difference would be detectable. When I download it via a windows front end, it's saves as a .zip archive. because it's not saved as a cr/lf delimited text, I cannot just click it, I have to extract it. Usually there's another log from helping someone else, so I have to delete that one first. After extracted, I have to navigate to it and right click it to open it with a different viewer. Sure it's not all that hard to do. Yet wading through the forums helping people in my free time and having to always cut, paste, navigate, then delete the extracted file and the .zip file starts to just get old. Maybe I'm getting old (Oh wait I am) or just bored with redundant operations.
December 12, 201411 yr When I download it via a windows front end, it's saves as a .zip archive. because it's not saved as a cr/lf delimited text, ... Changed the download function and zip the file in windows format as syslog.txt. Hope this helps your RSI problem
December 12, 201411 yr It would make it "quicker" for the user to view from any Windows OS as they wouldn't have to find a program that can handle Unix Linefeeds. Ah, is there a problem with Windows? I'm in a Microsoft-free zone!.
December 12, 201411 yr Author When I download it via a windows front end, it's saves as a .zip archive. because it's not saved as a cr/lf delimited text, ... Changed the download function and zip the file in windows format as syslog.txt. Hope this helps your RSI problem LOL, thanks, it just makes it quicker, click, click ,click and we're viewing. Other people can participate easier too. If people have issue with the default, a checkbox to save as dos.txt works too, but in the meantime it removes the redundant cut/paste/cleanups. Thanks! It would make it "quicker" for the user to view from any Windows OS as they wouldn't have to find a program that can handle Unix Linefeeds. Ah, is there a problem with Windows? I'm in a Microsoft-free zone!. For servers and automated tasks, it's Unix all the way. For desktop I use windows as many people here probably do. It's not even about the platform, it's about convenience of not having to extract the file for viewing. I use notepad++, but without it being syslog.txt, you cannot just click it, you have to extract it and rename it. It's really not that big of a deal until you do it many times trying to help people. In addition for the others who may want to jump into the fray, loading the file into notepad it becomes one long string. You have to use a LF aware delimited editor for review.
December 12, 201411 yr It's not even about the platform, it's about convenience of not having to extract the file for viewing. I use notepad++, but without it being syslog.txt, you cannot just click it, you have to extract it and rename it. Which is why I have a modified preclear script that puts ".txt" on the reports so I could just click on them in the folder. Sorry to go off topic.
December 12, 201411 yr Author It's not even about the platform, it's about convenience of not having to extract the file for viewing. I use notepad++, but without it being syslog.txt, you cannot just click it, you have to extract it and rename it. Which is why I have a modified preclear script that puts ".txt" on the reports so I could just click on them in the folder. Sorry to go off topic. I've done exactly that with my smartctl.sh and badblocks.sh wrapper. root@unRAIDb:# ls -l /boot/log/HGST_HDN726060ALE610_NAG1D* -rwxrwxrwx 1 root root 4576 Dec 1 22:06 /boot/log/HGST_HDN726060ALE610_NAG1D7TP.20141201-2206.txt* -rwxrwxrwx 1 root root 5121 Dec 2 01:05 /boot/log/HGST_HDN726060ALE610_NAG1D7TP.20141202-0105.txt* -rwxrwxrwx 1 root root 553 Dec 2 01:08 /boot/log/HGST_HDN726060ALE610_NAG1D7TP.20141202-0108.txt* -rwxrwxrwx 1 root root 0 Dec 11 10:54 /boot/log/HGST_HDN726060ALE610_NAG1D7TP.badblocks* -rwxrwxrwx 1 root root 5121 Dec 1 23:17 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141201-2317.txt* -rwxrwxrwx 1 root root 553 Dec 2 01:08 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141202-0108.txt* -rwxrwxrwx 1 root root 1952 Dec 4 00:41 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141204-0041.txt* -rwxrwxrwx 1 root root 4682 Dec 4 00:42 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141204-0042.badblocks* -rwxrwxrwx 1 root root 5360 Dec 4 00:42 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141204-0042.badblocks.txt* -rwxrwxrwx 1 root root 1952 Dec 4 00:42 /boot/log/HGST_HDN726060ALE610_NAG1DEKP.20141204-0042.txt* Plus I name my syslogs with a new syslog_archive script as hostname ccyymmdd-hhmm.txt so I can keep a few around. root@unRAIDb:# ls -l /boot/log/syslog* -rwxrwxrwx 1 root root 889228 Dec 8 07:34 /boot/log/syslog.unRAIDb.20141208-0734.txt
Archived
This topic is now archived and is closed to further replies.