Synology Install Unzip

2 views

Skip to first unread message

Geppe Warton

unread,

Aug 3, 2024, 5:23:57 PM8/3/24

to gedcurtbarsro

I had set a little docker project for myself and thought it may be fun to try and get azerothcore running on my synology.I have cloned the repository, but was unable to run the acore.sh script to build the docker containers as synology uses 7zip, and acore.sh threw an error because it couldn't unzip the archives.I wondered if it was possible for me to find out what scripts were attempting to unzip things, and change the commands to call 7z?

Hello, I am using synology for home assistant. So I am unable to install, supervisor, HACS, and all of that. I was interested in looking for themes. The Mushroom theme for example, but everytime i try to learn how to install it points me to HACS. Can this be done without HACS?

Please consider, that with the NAS that depending a type, a corresponding performance is available. The performance of the DS216j is such that the user has to tune Syncthing accordingly with corresponding requirements. The RAM memory has 512 MB, which limits the activities.

In any case, SynoCommunity is not paying attention. The reputable package from Kastelo is better (!), also in the concept. I have therefore deleted the SC package and have now switched to the Kastelo SPK at all Synologys, one of which is already installed.

After I added the source I can see no syncthing package. If I understand this correctly my 411slim NAS has an Marvell Kirkwood 88F6282 processor that uses the ARMv5TE architecture.Is it possible to provide a package for older ARM as well or is there a technical limitation?

In each Synology package is defined in the INFO. If I unzip the Syncthing package for Synology, in the INFO I found arch="$(pkg_get_unified_platform)", so is variable and not fixed. It seems the same as arch="noarch" is used, if the platform is irrelevant or should not restrict.

When installing the tvheadend Synology package and it asks you for a user name,make sure you enter one that doesn't already exist on your NAS. I looked into the code, and it's apparently trying to run "adduser" which fails if the user already exists. Apparently the package isn't watching for this error and continues to install; unfortunately, now no users can access it.

It seems, from an IRC conversation, that each new Synology tvheadend package installs into a new directory, and assumes to run under a username equal to the name of that package. Combine that with some packaging issues that potentially set ownership of the access control entries as read only for "root", then start a package called "tvheadend-40" as user "tvheadend-4.0", and you can see the fun.

The interface to change TvHeadEnd users is not very clear. If I remember correctly, one mistake I made is to not save correctly the changes I made. Be carreful also, because you have a user tab, and a password tab. Try to create multiple users, just to be sure that at least one will work :). And set all of them as admin. Once correctly connected, you could remove the unneeded ones.

The error line you have suggests that synouser cmd doesn't exist. Funny. Maybe there is more a path trouble, because this command is still the one recommanded by synology. (I know for example that unzip cmd disapeared, but it should not be the case for synousr).

I use Midnight Commander. It is a classic 2-panel file manager that you can run in a SSH shell. Old-school. Smells just like Norton Commander from prehistory but can do a lot more. You can have one pane be a local folder and another a remote folder over ftp. Or over SSH. You can unzip or zip or edit files, set owner and access rights or whatever.

I'm going to ssh from my desktop computer to owm(rp3b+), if I use midnight commander to move a big file between two USB drives, do I have to keep the computer on until it finishes moving or can I turn the desktop off after I give the move order?

Midnight Commander does not use any desktop environment, only a text based shell. So it works fine directly on a OMV NAS without any desktop environment. Or you can run mc in a terminal window on a client computer. Or you can run mc over SSH on the OMV NAS in a terminal window open on some computer running some desktop environment. In the LAN or from the other side of the world.

If you use the screen utility you can create a persistent shell environment that will keep running commands, including mc moving files, even if you close the connection to the shell. Close the desktop shell window or terminate the ssh connection or whatever. Later you can reconnect with the persistent shell to see if mc is finished.

This is drawback of omv vs synology or qnap... Why i so hard to have a file manager on omv ??? This method (mc over ssh conection or another method ... ) request that on every pc you try to connect to omv to have or install putty or winscp....

Use Krusader in Docker as suggested by @KM0201. I've quickly tested and works quite well. You have the complete GUI as it uses VNC.
It's the most complete I've tested so far.
(I don't want to use SSH over the internet)

An ssh client has been enabled by default on Windows 10 since the April 2018 update... And is installing putty or winscp really that hard? And you don't even need those. You have a file manager on your os if you create smb or nfs shares that the client can connect to.

Write one if it is that easy. Synology and QNAP have hundreds of people working on their NASes. OMV has one core dev and basically one plugin dev. I don't understand the need for one so I won't be writing one. Install webmin if you really want a web-based file manager.

Fortunately there's way to avoid this. Unfortunately, it's not something you can easily memorize. Or, I certainly cannot. Credit is to Joakim Nohlgrd, who posted this in an answer to a question about this question on Superuser.com.

You can modify the command to your liking of course. If, for example, your archives are in 7zip or RAR format, you could replace the unzip command with 7z (7za on Debian-based systems, see footnotes). Here's an example that includes specifying what path to extract to:

I have had situations where I needed to create individual archives of each folder inside a certain directory. If you ever need to do something similar, here is an example using 7zip to do exactly that:

If you are running a Debian-based Linux distribution (ie. Ubuntu), you can easily install whichever tool you need to use. For ZIP files you could rely on unzip as the examples above show, or you could install p7zip for compatibility with more archive types (ie. 7z, RAR, etc.). On macOS unzip is already pre-installed, and you can install 7z using Brew.

In the previous article of this series I provided steps to install and run the Nagios network monitoring utility on either a Synology DiskStation DS1813+ or a DS412+ for the purpose of pinging network devices to verify that the devices respond to ping requests. That article may have seemed a bit out of place on a blog that is primarily intended to include notes about using Oracle Database. In the previous article I hinted that there is a check_oracle plugin for Nagios, suggesting that a Synology DiskStation DS1813+ or DS412+ could be used to monitor Oracle databases.

Connect to the DiskStation using Telnet as the root user (see the previous article for Telnet connection directions). For consistency, the .zip files for the Oracle Instant Client will be copied to the downloads directory that was created in the previous article. We will create an oracle directory in the downloads directory:

Next, the downloaded files for the Oracle Instant Client are copied from the config share that I created on the DiskStation (to allow transporting files from a desktop computer) to the /volume1/downloads/oracle directory that was just created, and then the Oracle Instant Client files are unzipped, which automatically creates the instantclient_11_2 directory:

Now that we have verified that the Instant Client version of SQL*Plus works from the DiskStation, we will create a simple SQL script to verify that the Instant Client version of SQL*Plus is able to accept script names from a command line. The script will be created in the same directory where the Oracle Instant Client is located (see the basic directions for using vi, as found in the previous article):

The results from the SQL statement should display in the Telnet window, and then the normal DiskStation prompt should appear. If the database instance was not running at the time of the execution, you would see something like this rather than the results of the SQL statement:

Additionally, we need to instruct Nagios that there is now an additional configuration file to read when starting. Save the oracle.cfg file and exit vi. Execute the following command:

Save the nagios.cfg file and exit vi. Since we have modified the Nagios configuration, we must restart Nagios. Find the first Nagios process ID, then kill that process (as was described in the previous article):

Nagios should be writing log entries to a file name nagios.log (as defined in the nagios.cfg file). The tail command permits viewing the last few (100 in this case) lines from a specified file: