How can I list the features of a pool?
With zfs get all <pool> I can see the list of properties and their values of a pool. But not the features: https://openzfs.github.io/openzfs-docs/man/7/zpool-features.7.html
Google brought me to your question because I was wondering the same thing... except when I get all, I see both options and features.
Feature syntax has appears to have a feature#<featurename> appearance. All of my test pool's features were listed after the options, at the bottom of the wall of text that zpool get all generated.
Related
While mindful of this answer from 2017...
For Kibana 7, is there an updated way to jump from a Dashboard to the Discover tab?
So that I can see the raw documents that support a visualization?
To some extent, yes, there is a possibility to make dashboards interactive and open panel data to Dashboard, something what you are looking for. However, this will only work if your panel uses just one data view.
For more information on configuring this, please refer to: explore-underlying-documents.
If you want to drill down into the documents from, lets say, data tables, you have that option as well, please read: create-drilldowns
First foremost: I am aware that this is not a general Typo3 bug/error per se, as I have working installations. I am hoping for hints/help in finding the error in this installation, as it's way too big to just set it up as a new installation.
I have an erronous Typo3 10.4.17 installation (updated to 10.4.x, no fresh install)
Problem: Edited elements in workspace are not shown in the Frontend preview (opened via "Show webpage" or other basic means in BE) nor in the BE View-module.
Additional info #1: They are however shown when preview links are generated via "Generate page preview links" and those are viewed.
Additional info #2: Changed elements only become visible after publishing them & clearing Cache
Additional info #3: Clearing any Cache does not make them visible in the preview
After comparing all settings I could think of to another working installation I decided to delve into the core in search for a hint/solution and got stuck there at following point:
TYPO3\CMS\Workspaces\Controller\PreviewController
Line 130 $workspaceItemsArray = $this->workspaceService->selectVersionsInWorkspace()
As well as:
TYPO3\CMS\Workspaces\Service\WorkspaceService
Line 220 public function selectVersionsInWorkspace()
At this point my edited workspace version of the element does get retrieved. selectVersionsInWorkspace() does get called when viewing the preview.
While the PreviewController does not further filter the staged elements, they are not displayed in the Preview.
I am looking for any hint as to where selectVersionsInWorkspace() might still be filtered or other hints as to possible reasons/solutions for this problem that I may have overlooked.
Just when I decided to post to SO a co-worker found the reason...
As it's a big installation we use a dev-domain as admins and each website (over 100) have their own domains which are also set as base in the Site-config.
Only when the preview is opened as either the base or a baseVariant the workspace-elements are displayed at all. In older version the elements would still be displayed when opened via other associated domains, just sometimes not 100% accurately.
Letting this stay in case anyone ever has a similar problem and is hopefully able to find this.
I think only one thing is missing...
but I do not get this point :p
i created an user and I created a group, both didn't work
What I want is a group with specific rights, one with read and edit rights and one with only read rights, but all only works for the "root page"
how can I inherit this to the following pages?
All the things from older versions of TYPO3 do not really work at my version (my version is 7.6.14)
Update 1:
Okey, I could set the rights by hand for every single page in the access category. But I think there should be a possibility to inherit the rights to all the subpages?
At last it may only be one checkbox ore option I have to activate?
One picture to make it more clearly what my problem is:
For those who don't understand german, "Berechtigungen" means access and "Tiefe" means depth.
Solution
I finally got it and it and it is working fine.
I just need to set the depth at the right place here:
One more hint: be_acl is a good extention, if you need more than one group for a page or more specific rights for different users.
Maybe the group does not have access to the subpages?
In the backend under System -> Access you can change the ownership of pages -
owner, group and all.
When editing access control of one page, you can change the depth to automatically adjust subpages.
You can find a really good article about right management in the blog from Marcus Schwemer here: https://typo3worx.eu/2017/02/typo3-backend-user-management/
For other things it would be useful if you could provide a little bit more informations about what does not work?
For example it could be that your user has no access to the page tree, if this is the case there is an extra "Access" Backend module. You can find more information about this here.
I'm having a very interesting problem w/ content appearing on my publish instance. Let me just run down the situation and see if anyone can help.
I have an author and publish instance set up.
Authors have and still do successfully replicate items from Author to Publish with no issue.
All of my code base has been migrated over, my jars are fine -- i even rebuilt the individual jars in the publish instance crx just to make sure.
------- now for the issue.
I went to publish a new page and it did not show up on the publish instance. It's not a new template or component type, just another page to add to the list. These are the actions I took and what i found. I currently have 2 publish instances set up, but will refer to them synonymously as "publish" since their states appear to be identical.
Activated to publish -- did not show up in publish
logged into publish/crx/de/index.jsp to make sure it was replicated properly.
the content did make it fine and is in the proper path in /content
The ACL and access control permissions are the same as all the other content nodes of the same type. (Just to note, those content nodes are perfectly viewable).
No stacktrace errors in my logs. However, when going through the dispatcher I get this error: org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension js, cannot render resource JcrNodeResource, type=XXX, superType=null, path=/content/XXX/jcr:content
I went ahead and logged in as admin in my publish/crx/de and hit the content page in question and everything looked fine. What this means is the content is available to administrators but not anonymous users.
edit: I made sure to check the anonymous context in all 3 instances -- both publish instances directly and through dispatcher.
From here I figured it had to be an issue w/ the access control, but the new node has identical permissions to nodes that are available to the anonymous user context.
To check if it was a matter of replication, I went and deactivated some of the other similar nodes, saw they disappeared, reactived them and saw them come back. Following this train of thought I deactived the group (old nodes + my new node) and then reactived them -- all the old nodes showed up, and still the same permissions issues w/ the new node.
Is the access control available anywhere else? I'm curious if there are other places for me to look at in order to figure out what's wrong with this piece of content.
thank you,
Brodie
You can set "read" permissions for the group "everyone". Ultimately, you will want to put a dispatcher in front of your publishers, and prevent public access to your publish instances directly (preferably sitting behind a VPN).
This means that your dispatcher will be denying access to /apps anyway, and your instances will still be secure, and the ACL for the publisher won't really matter as long as an anonymous user can render the page under /content
Have you tried hitting the page directly as an anonymous user on the publisher (bypassing the dispatcher)? That would help you rule out whether it is a dispatcher issue.
This article may also help: http://forums.adobe.com/message/4263731 It include this:
"The issue was that after creating a new site on an author instance,
when viewing it on the publish site the page was not rendering
correclty. The visible symptom was that initial HTML tags (for HTML,
HEAD, META, and BODY) were being generated, but the content was not be
filled in. I did Activate my content properly, however, because it
was a new site, and I had generated new components and site templates
which resided in the "apps" folder and assets in the "etc" folder,
they were not available to be rendered and so the HTML page was blank
(because they could not be found on the publish instance). What I did
was use the "Activate Tree" under the Tools section to publish content
in /content/mysite. What I missed was using the Activate Tree to
publish items I had created in /etc/designs/mysite and /apps/mysite."
So this is on solution I found, but I don't feel like it is the best solution.
The root issue was that access control was restricted on the Views of the component. This is because /apps has a default deny to read for the "Everyone" group.
I changed this, but was told that of cq5.4 this was put in as a security precaution.
So as this fixes my problem, I fear it may introduce new ones. I'd like to get some more responses before resolving this out.
WEN U ZIP FROM PACKAGE MANAGER FOR USER AND GROUP PERMISSIONS ADD ALL THE NODES WHICH U HAVE WITH THE NAME OF "REP:POLICY"'S AND INSTALL IN NEW CQ
I'm using the github issue tracker for the first time, and I'm trying to manage a set of about 50 open issues. I would like to filter the set using standard Boolean queries over labels. But all I can figure out how to do is AND queries.
For example, I can show all issues that are labelled both view/controller and easy meat. But I do not know how to do any of the following queries:
Show me all open issues that are labeled view/controller but are not labeled easy meat.
Show me all open issues that are labeled either major refactoring or needs thought.
Show me every open issue that does not have any label.
I've searched and I've RTFM, and I can't find a way to ask these kinds of queries. Are such queries even possible? If so, how does one ask them?
This is possible since GitHub introduced the advanced filters.
Show me all open issues that are labeled view/controller but are not labeled easy meat.
is:open is:issue label:"view/controller" -label:"easy meat"
Notice the - before label: which says do not give me the issues containing this label.
Show me all open issues that are labeled either major refactoring or needs thought.
This is not supported (using label:A label:B means A and B instead of A or B) but you can do two different queries:
is:open is:issue label:"major refactoring"
is:open is:issue label:"needs thought"
Show me every open issue that does not have any label.
Use the no:label query:
is:open is:issue no:label
As additional info, you can refer to the GitHub documentation. And, https://github.com/issues can be your playgroud–being authenticated, you can search all the issues from repositories you have read access!
Not possible, at least using the GitHub Web app only. There may be 3rd party issue-management Web apps that do this (via GitHub API), but I'm not aware of any that do exactly and only what you want. Check out:
http://gissues.com/
http://huboard.com/
http://githubissues.herokuapp.com/
https://zapier.com/zapbook/github/trello/ (trello integration)
There are ways to achieve nearly what you want using formatted issue naming + searching, as described here:
https://softwareengineering.stackexchange.com/questions/129714/how-to-manage-github-issues-for-priority-etc