Notices tagged with nas, page 2
-
Hurrah. I've cleanly overridden a Wordpress function's operation by overriding its apply_filters() with my own. That took a bit of figuring out (quite a while ago since I've done similar things), but it's far more 'lightweight' than installing a 3rd-party plugin. So now for a comment it no longer shows the user's login but the 'display_name' instead. (I can (should?) probably do the same for posts as well. :)) #DIY #wordpress #security #nas
-
@tobias Ha! I'm only seeing this now... I didn't now about it but it was what I found in ASUSTOR App Central. One can't just install *any* software on the box because it's not a normal Linux system, though I suspect PHP applications will generally be OK. So far, I like SQL Buddy, clear and simple and the UI is easy to learn. #nas #SQLBuddy #asustor
-
@mk After a lot of futzing around with phpMyAdmin I followed one suggestion I found: stopped #mySQL and made a backup of the database *files* (simple local rsync), then UNinstalled phpMyAdmin. Planning toe-install it I noticed ASUSTOR's App Central also has something called SQL Buddy - so I installed that. And it let me log in without any problem. It's simple. It works. That's all I need. I supect #phpMyAdmin has just become more and more complex to the point where it's become fragile... So it's #SQLBuddy for now. Dropping the 'pspmyadmin' database... #nas
-
@mk This morning, with more entries in the cron log (and even the system log) I'm starting to notice some odd patterns... 1) after ONE manual ntpdate update 23:24 , I am seeing THREE updates about an hour later (all at the same time 00:30) in syslog - but only TWO entries in the cron log - after that, no more entries. 2) Meanwhile, at 23:02 (BEFORE the automated ntpdate) an EXTRA crond was started, while the old one apparently continued running. 3) From then on, the automated updatedb is successful for the NEW crond while the old crond (not surprisingly) encounters a locked mlocate.db file. Both crond's do ONE ntpd update at 00:30 - it's not clear where the third one (recorded in syslog) at the same time came fery hour one successful and one failed updatedb - but nothing else (no ntpdate) is recorded in the log... #nas #cron #confuzzled
-
@mk ...and slowly, slowly, am I getting this nice #NAS box called Hal a bit more under control. Lots of riddles and #frustrations today, but also #learning, #discoveries, and #progress. In all, a good day (in spite of seemingly having a cold!). And more things to figure out #tomorrow. Like: *which* changes that I made *actually* made cron start writing to a log file? and: how do I replace a @reboot crontab rule because BusyBox doesn't support it? There are probably 2, maybe multiple ways... #hammock, for now!
-
@mk yay! I created the 'missing' directory '/usr/builtin/var/mlocate' (where the database should go), then after more grumbles also created the *group* 'mlocate' and finally ran 'updatedb' once more which now actually managed to create the database! And now the 'locate' command actually works! #NAS #locate #mlocate #updatedb Next up: attempt to add updatedb (permanently) to the crontab... (but first check if the database itself survives a reboot) /cc @r7
-
@mk I also haven't figured out yet if I can make bash (ash) scripts an execute them via cron (so Hal could *pull* backups); otherwise I think I'll have to script *push* backups to Hal. It does have an rsync server and SSH (the latter apparently not user-configurable). Hard to know where to start... #NAS
-
@sazius and I just thought of another possible option: OwnCloud - I have it installed on the #NAS but not set it up yet (so: also not quickly - but it might at least work for 'remote' backup
-
@mk @sazius meh. editing the sshd_config on the #NAS works (the changes stick, even after modifying the port via the web UI) - but the 'AllowUsers' line I added is *not* accepted. So I cannot login as another user, and thus *must* login as root even though I want to forbid that. :( So, my only 'extra' security for SSH is the non-standard port. #nothappy
-
@sazius real directories is what I understand rsnapshot does. Maybe attic, too. Locally (on the #NAS) I'd really like to have 'real' files, or at least they should be accessible as such. But from my reading I also understand that rsync is much faster than obnam, and obnam actually isn't very good at dedup either. No idea how that compares to attic, though. https://attic-backup.org/ http://blog.karssen.org/2013/01/04/comparing-rsnapshot-and-obnam-for-scheduled-large-backups/
-
@sazius major problem: I still need to tweak the server itself because I don't like to have to login to the server with the root (or admin) account. And I haven't found where exactly that restriction is defined. :( I'd be happier if I could block direct root access and rename the "admin" account. Ging to mull it over a bit and then (very carefully!) do some experiments *sigh* #NAS
-
@sazius It seems Attic also has a 'deduplication' algo that sends only changed chunks of files; this is important since I will have to use it over slow Internet connections. Attic supports encryption, as an option. But another factor is I cannot just install 'anything' on the #NAS - it's embedded Linux, and comes with (installable) rsync; there's a user-suported package for rsnapshot (but the archive is called "unstable"); Python and Perl are available, too, so rsync + scripting in one of those should work.
-
@sazius great - looking that up, I'm also finding Attic, Duplicity (uses encrypted tar) and bup (uses gitpackfile format); have you heard of any of those or tried them? Encryption (for now) is only relevant for transport (SSH or so) across Internet, not for storage, since it goes to my #NAS
-
still tweaking details such as permissions, but I've now got to the point where I can (manually) write backups from two different computers via NFS to the #NAS #babysteps #gettingthere :)
-
while I'm at it and have a good (NFS) connection between Dennis (Live Mint/Cinnamon) and the #NAS, I'm finishing some initial backups. Once that's done (and checked) I'm ging to install it. #networking !linux #distros #byebyefedora
-
wonderful - backup of Dennis's root partition to the #NAS is now also finished! (So I can now overwrite it all with a new install!) now I can sleep without worries, and maybe #tomorrow I'll install Linux Mint with Cinnamon (after backing up some settings of my Live session!).
-
in other news: busybox makes me very unhappy - it seems I can never do the things I need to do (such as mounting a drive for a particular user) #NAS
-
@mcscx what is the .2 and the .1 in that? FRITZ!box's IP is 192.168.178.1; btw, the LAN works: I just found I could connect to the #NAS via samba (at least I can see the shared folders)
-
Enough poking around for today - my brain absorbed quite a lot of information, but I STILL don't know how the #NAS restricts login to root and admin only. It may actually be controlled by a specially-compiled sshd (?) - I can't think of anything else. :( I'll have a small bite and relax a bit before retiring.
-
OK, I just figured out that the start/stop/etc script for SSHS on the #NAS treats 'restart' and 'reload' the same: do a stop followed by a start (and stop does 'killall sshd'). I assume this is why any restart of sshd disconnects open sessions. Unless I misunderstand the process or the script, of course. #ssh #learning #script