@jospoortvliet said:
using letsencrypt right now on my home server, btw. Have a cron job set up to update the cert every month or so, with an easy tool: ACME. Simpler than the 'standard' tool from Lets Encrypt, if you ask me. Go check it out at https://github.com/hlandau/acme
I had a good laugh when I spotted the ".travis Try to speed up travis" Apparently I'm slowing things down, tho I do agree that speeding me up would be a good thing 
@scottalanmiller said:
Under 100 PMs now!!!
I take it the SPAMSAM project didn't go anywhere? What an oddity, an online community that can recognize a joke comment for what it is.
@Breffni-Potter said:
@Kelly said:
We've already had one agency tell us that we cannot use any Lenovo hardware in support of their systems.
Falls off chair
An agency actually said no to Lenovo products?!?
Anyone paying any attention at all to security would be doing that right now. Not surprising at all.
@DustinB3403 said:
@JaredBusch said:
@scottalanmiller said:
Ah, the issue is that you want to use a relay. might want to try skipping the relay.
Yes, using a relay is a much different thing than sending mail directly.
@DustinB3403 You just worked around an issue without even know what your issue was.
I know,
I also figured out the Unicorn problem that North Korea has all by myself.
YAY!
So long as we're not going to candy mountain here....
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I definitely understand abstraction in RAID 10, 5, 6, etc, but with RAID 1 it seems like unnecessary overhead.
Why? Why do you feel it needs to exist for the others but feel that RAID 1 is unique? Abstraction is abstraction. You have RAID or you do not.
Could you do RAID 1 without any abstraction on the disks themselves? Yes. Could you do it and still have the expected features like the disk itself knowing about its RAID? No.
In RAID 1 does that matter? I definitely understand it's need in the other RAIDs.
RAID has an abstraction. That you are using RAID 1 doesn't change that. RAID 1 is not a special case in any way.
Are you thinking that RAID 1 implementations specifically drop the RAID abstraction at the disk layer and act differently than all other RAID levels, even within a single implementation?
This has been my personal experience. The few times I've needed two, I could just remove one drive and slave it up to another computer and assuming the file system was known you could mount it and it just worked.
Granted this was probably 10+ years ago.
So long as it's on the same type system, this is still true @Dashrender. Most low to mid range storage boxes use mdadm for the actual storage, so connecting a drive from one of those to a Windows or MAC computer won't work.
In this case, if they put the old drives in the new NAS, the data could well just be gone, unless they pay for some expensive data recovery something or other.
You probably want to boot into a live Linux distribution of some sort. It's that or jump through some hoops to present the bare drive to a Linux VM in Virtualbox. That's your best chance at actually reading something from that drive anyway.
@kamidon said:
As far as Lenovo, that secret chip or whatever it was they sneaked into machines should have bankrupted them.... Though the reality is, it obviously hasn't done much. Am I missing something though, has Lenovo done anything more than the first incident I'm aware of?
They're having at least 1 security flaw per month released. The latest one was "We changed a hardcoded password, so that's not a problem any more." Only everyone figured out what the new password was right away.
@scottalanmiller said:
Why do you need a user account? Have you tested the mail command?
Great point. Have you tried sending yourself an email from the command line yet?
echo "Test Email" | mail -s 'test' you@yourdomain.com
@DustinB3403 said:
While I wait for that drive to arrive, I'm going to figure out how to configure email alerts for the mdadm array. Seeing as this would be incredibly useful to have.
Since I can't sit here watching the cat /proc/mdstat....
No remote ssh access?
@johnhooks said:
@Lakshmana said:
My favourite linux command is "ls"
"cd"I use those quite a bit also.
I use them all the time, doesn't mean I like them. At least ls is shorter than dir.
@johnhooks said:
@travisdh1 said:
@johnhooks So, you just use
pv dd if=/dev/urandom of=/dev/sda bs=512kThat's actually really handy.
YOu have to pipe it in, it's a strange syntax
dd if=/dev/zero | pv | dd of=/dev/sdaAlso any flags or arguments go before the first pipe.
That is a bit odd. Still handy tho.
@johnhooks So, you just use
pv dd if=/dev/urandom of=/dev/sda bs=512k
That's actually really handy.
@scottalanmiller said:
Haven't used PV. I do use watch a bit.
Because of this thread I've been conditioning myself to use glances. It really is very useful.
Glad to hear someone else like it!
@DustinB3403 said:
@travisdh1 said:
@DustinB3403 Should be, mdadm still works the same way.
Thanks, just being extra cautious to ensure this works smoothly.
To remove the disk from the array I should have to simply type
mdadm --manage /dev/md0 --fail /dev/sdcand then
mdadm --manage /dev/md0 --remove /dev/sdcAt this point I should be able to shutdown the server, remove the disk and add it's replacement with
shutdown -h now
Yep. After putting a replacement drive in, just add it back.
mdadm --manage /dev/md0 --add /dev/sd?
I like to keep an eye on the rebuild process with:
watch /cat/proc/mdstat
The array should be back to normal.
@coliver said:
One of our fire alarms have been triggered for the last three nights. It goes off for 5-10 minutes and then stops. Swapped it for a different alarm downstairs... same thing happened.
Same location, or same fire alarm?
@DustinB3403 Should be, mdadm still works the same way.
@johnhooks said:
He also told me be stopped using CentOS at 6 because he didn't agree with the new changes. I assume he means systemd, but he couldn't remember the name. I'll give you a months pay if he can explain any differences between init and systemd.
That's off the top of my head.
Doesn't mean it's not still crazy.
@Danp said:
@scottalanmiller I think so... command was
sudo nano /etc/crontab.
I normally have it in /var/spool/cron/crontabs/root, /etc is normally just settings.
Debating problems with SAM instead of watching more security camera footage. Just can't take much more of watching these things.
@scottalanmiller said:
@travisdh1 said:
@DustinB3403 said:
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
Try adding the XO installation directory to the PATH statement in that crontab. I'm betting it doesn't know where to run things due to the limited environment the system crontabs run in.
If it needs the PATH, then the command is wrong. It should not know where it is.
In my limited experimenting, npm isn't the best implementation of a program. Then we're also dealing with a crontab not running a script/program that we know runs outside of the crontab. At least to me, this just screams that something is missing from PATH at the point it's being run.
@DustinB3403 said:
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
Try adding the XO installation directory to the PATH statement in that crontab. I'm betting it doesn't know where to run things due to the limited environment the system crontabs run in.