July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted.
July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted. :'(
July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted. :'( :'( He did say, 5.0... I would be happy with dedicated state messages at this point. I can code around that. But right now I would have to guess at the state by scraping syslog and poking around the system.
July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted. :'( :'( He did say, 5.0... I would be happy with dedicated state messages at this point. I can code around that. But right now I would have to guess at the state by scraping syslog and poking around the system. The routine I coded is working perfectly, stopping processes before letting the array stop and starting them after the array starts. It has been in place for some months now, but I too am waiting for real triggers. Joe L.
July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted. :'( :'( He did say, 5.0... I would be happy with dedicated state messages at this point. I can code around that. But right now I would have to guess at the state by scraping syslog and poking around the system. :'( I would even settle for /proc/mdcmd not showing "mdState=STARTED" once array-stop procedures are initiated. (I hate to say such a thing, but my loyalty to Limetech is steadily thinning out.) Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well.
July 3, 201016 yr Probably will be a 4.5.5 to add a couple drivers and some misc fixes. I can also throw in a few script call-outs as well. Unfortunately, there were no call-outs added. :'( :'( :'( There is new logic in rc.local to run installpkg on ANY files found in /boot/extra before the "go" script is invoked that is new, but that is only good if the installpkg does everything needed and if it does not need to reference any of the disk drives, since they are not yet mounted. It does not help to stop and re-start processes that are referencing the data disks prior to the array being stopped or after the array being re-started, but not re-booted. :'( :'( He did say, 5.0... I would be happy with dedicated state messages at this point. I can code around that. But right now I would have to guess at the state by scraping syslog and poking around the system. The routine I coded is working perfectly, stopping processes before letting the array stop and starting them after the array starts. It has been in place for some months now, but I too am waiting for real triggers. Joe L. I know, but I would want a real state definition so we're not scraping and guessing. The finite state machine script was cool, but I had the feeling it was assuming things. As user needs become more sophisticated, how and when they interact becomes more important.
December 7, 201015 yr rsync backed by a gui... for less techno users. Let Rsync sync your files between computers at home, and over the interenet to an offsite location. Sort of what dropbox does. Can we have dropbox on unraid?
Archived
This topic is now archived and is closed to further replies.