官术网_书友最值得收藏!

Pinning publishers

It's not rare when the system has many configured publishers and it becomes necessary to ensure that a package that was installed from one publisher is not updated from another.

Personally, I've seen some situations where an installed package from a very reliable repository was corrupted by an update from another, not-so-reliable repository. That's funny. The same package exists, and it can be installed from two different repositories, but one of these repositories is less reliable, and eventually, it can offer a bad package. This is where pinning becomes useful. I guarantee that a package installed from a source (repository) will always be updated from the same repository. Let's learn how to do this.

Getting ready

To follow this recipe, it's necessary that we have a system (physical or virtual) running Oracle Solaris 11; we log in to the system as the root user and open a terminal. Access to the Internet is optional.

How to do it…

To pin a publisher, we type the following:

root@solaris11:~# pkg set-publisher --sticky solaris

Undoing the configuration is simple:

root@solaris11:~# pkg set-publisher --non-sticky solaris

Note

Any new publisher will be pinned by default.

From now on, every package will always be updated from its original repository even if an update is available from another one.

An overview of the recipe

This is an interesting situation. Usually, an administrator needs a package offered by two different publishers, each one with a determined level of reliability. In this case, we need to choose one of these and create a "sticky channel" to it.

主站蜘蛛池模板: 河池市| 乌兰察布市| 泰和县| 深水埗区| 水富县| 马尔康县| 永定县| 纳雍县| 定远县| 米泉市| 南城县| 张北县| 三门峡市| 左云县| 方城县| 西城区| 洪泽县| 甘谷县| 广水市| 巴塘县| 隆尧县| 宝清县| 阿尔山市| 广东省| 伊宁县| 六枝特区| 芷江| 宜川县| 正定县| 嘉兴市| 绩溪县| 乌拉特中旗| 天台县| 唐山市| 皮山县| 蓬溪县| 宣武区| 博野县| 保康县| 阳原县| 河间市|