Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Sorry if this was covered and I missed it. I'm running OmniOS 151022 and after months and months of 'pkg update' always reporting nothing to do I thought it was strange to borderline suspicious and in digging around it looks like OmniOS is basically EOL? Is that true? If so that would...
I fixed it, but I don't know exactly what did it.
It might have been creating /reconfigure and rebooting. I thought that didn't work before but perhaps it did. If anybody else stumbles on this I suppose that's worth a try. I know I did have to to manually run `sudo devlinks` after reboot and...
Gea,
Yes as far as I can tell everything otherwise works fine. I do not recall having this error immediately after install.. it just crept in at some point a day or two later. The use of /dev/null will work b/c it's currently set 666 (777 on the symlink but that's always reported for symlinks...
Installed omnios-r151020-4151d05 over the weekend. Everything seems to be up and working but I'm getting this message when I log in. I saw the notes about doing chmod 666 /dev/null as root but that returns the same error in the console.
Thank you. I'll look at updating the OS then, I rather expected that was probably the issue.
I never updated the current OS through the package manager because when I did things would break (I can't recall now what exactly, but I did need to roll back the BE). Is OmniOS pretty good about...
Gea,
Love napp-it as usual!
Question. When I download/activate 17.01pro the "pro monitor" stops working. When I run 16.08 it works fine. I poked through menus and such but can't seem to find if there's a toggle I'm missing.
Here is the info on my about page.
napp-it Appliance: PRO...
Thank you. Is aclmode=restricted set on the server or client side?
EDIT: Oh I see, I think you're talking about in the filesystem. That's not an NFS option right?
This might work, but unfortunately in napp-it when a job has an = sign, that seems to cut off the display of the full command in the UI. I checked and the full command is still there in the job's .par file but I don't have the best memory so 6 months down the line I'd forget what the command is...
Multiple linux applications mount various directories via NFS and make chmod changes. A single offsite backup application needs to read everything.
The linux applications setting chmod=xx0 turn in to ACLs that prevents the backup application connecting via samba from reading the directories...
I use my NAS as an NFS mount for various applications. Some of those applications (coincidentally all linux based) apparently want to chown and/or chmod files. The NAS is then interpreting those changes (I assume some interpretation) in to ACL changes. The application still works fine...
The PCIE lanes don't explain the limit. 2x PCIE 1.0 would be 500MB/sec, 2x PCIE 2.0 is 1,000MB/sec. You're falling right in the middle, so you can't be on 1.0 or you wouldn't see 750 and since you must be 2.0 or greater you must have at least 1,000MB/sec in bus bandwidth which is greater than...