Talk:Pacman/Tips and tricks
pacman-optimize on SSD
pacman-optimize only tries to reduce fragmentation of the files right? If that is the case perhaps we should include a note that this probably won't help much on an SSD. —This unsigned comment is by F4hy (talk) 18:27, 29 March 2013. Please sign your posts with ~~~~!
Should the wiki no longer recommend this package? -- I'm guessing it shouldn't.
Also, is pacman-optimize less important than in the past? -- I am genuinely unsure about this.
- The maintenance of AUR has nothing to do with that of itself, it is packaged separately and even in the AUR. Anyway, I'd keep the section until pacman-optimize is removed from .
- The reasons why it is not very important nowadays are improvements in pacman itself (mentioned in the ML post linked above), increased speeds of HDDs and the advent of SSDs.
- -- Lahwaacz (talk) 22:18, 2 March 2015 (UTC)
Pacman/Tips_and_tricks#aria2 doesn't work without leading slash, i.e.
-d / turning file names to
//var/cache/.... The article mentions this, but it doesn't mention why. -- Alad (talk) 05:28, 16 October 2015 (UTC)
- You would have to go way back to track this. It seems to have worked without
-d /even in 2006: , .
I guess that simply nobody asked the right question...-- Lahwaacz (talk) 12:30, 16 October 2015 (UTC)
- Oops, it does not work without
-d /. Then the problem must be on aria's side, which expects a file name for the
-ooption, which is then catenated with
-dinto the full path. Assuming that
-ddefaults to the cwd,
/var/cache/would appear twice in the result. -- Lahwaacz (talk) 12:43, 16 October 2015 (UTC)
I still think we should warn people not to symlink /var or anything under it. It leaves the whole system unusable because if the cache disappears during a pacman transaction, you're left with missing /usr/lib libraries, and nothing works, including pacman itself. This is a serious enough problem that it can take hours to figure out how to recover. If the wiki had mentioned this problem it would have saved me a lot of time and effort, and I'm not the only one who has run in to this. It is not, however, considered a bug. See https://bugs.archlinux.org/task/50298. JimRees (talk) 23:15, 29 April 2017 (UTC)
- This revisions says that: . But to make it more clear:  -- Rdeckard (talk) 00:13, 30 April 2017 (UTC)
- Thanks for the background information. I was not aware of the bug report and now clearly understand why you altered the section the way you did. I hope the recent change is sufficient for you. Since every misbehaving program might leave a system unbootable if it plays a role in the boot process, it should be unnecessary to add this redundant information. However the problem you described is still severe and I hope you agree that the recent edits made to the article do the topic justice. Thanks for clarifying the topic and adding this to the article and sorry for reverting your edits at first. -- Edh (talk) 21:07, 30 April 2017 (UTC)
local repository database extension/compression recomendation
If you opt to not compress a pacman database, the files database can become very large, 10x larger than a gzipped one in my case, which cause issues when trying to update the local pacman files db (pacman -Fy) since apparently there is a max (expected) size. Should we include a warning about uncompressed databases?
Use a new nginx.conf for Dynamic reverse proxy cache using nginx
I propose to replace the current nginx.conf with an improved nginx.conf and update the section. The new config doesn't make the upstream servers directly available on the network and it allows having mirrors with different relative paths to package files. It also removes directives that are not needed and has some other minor cleanups. I've been using a similar config for a few months now without any problems, so I believe it should be fine. Noctavian (talk) 16:05, 28 February 2019 (UTC)
- What do you mean by "The new config doesn't make the upstream servers directly available on the network"? -- Lahwaacz (talk) 20:54, 28 February 2019 (UTC)
- In the new config the server blocks for the upstream mirrors are set to listen to 127.0.0.1:800X. Only the computer that is running the nginx cache can send requests to 127.0.0.1. Other computers on the network can't. The current config exposes the upstream mirrors to the network, a nmap scan will show the 8080 port of the cache as open and the ports 8001, 8002, 8003 of the upstream mirrors as open. One can browse to cache.domain.example:8002 and have direct access to whatever package mirror website is used by the cache bypassing the cache config order and locations. The upstream mirrors don't need to be available to the entire network for the cache to work; they only need to be available to the computer that is hosting the nginx cache. I believe ports should not be left open on the network if they don't have to be open. Noctavian (talk) 08:37, 1 March 2019 (UTC)
- I have written a draft for the section update on my user page. I made some small changes to the config file since last week, added comments and mirror examples and turned off IPv6 address resolution to prevent some errors that can happen sometimes. Suggestions.are welcome. I haven't seen objections to my proposal, so I'm going to wait a few more days for feedback and then update the section on the main page with my draft and the new nginx.conf file if that's ok. Noctavian (talk) 11:43, 8 March 2019 (UTC)