posix
Here are 680 public repositories matching this topic...
When singular items are missing we say "does not exist" or doesn't exist".
When singular items are present we say "does exist" or "exists".
Yes, English can be difficult.
https://github.com/acmesh-official/acme.sh/search?q=%22doesn%27t+exists%22&unscoped_q=%22doesn%27t+exists%22
Text says "doesn't exists".
Ref also : https://github.com/acmesh-official/acme.sh/search?q=%22does+not+exists%22&
Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Describe the bug
README#Installation-guide Step 3 contains command:
go get github.com/chrislusf/seaweedfs/weed
It builds weed here without compiler errors, but weed binary panicing same as in #1058 :
panic: /debug/requests is already registered. You ma
Is there some documentation or user guide for this project?
I've just spent half an hour figuring out how to mount with goofys inside a docker container -- it's not a big deal, of course, but I'd like to write it down, so that others can figure it out faster.
For example, ParamExp has a Name field of type *Lit, but it can never be nil. The reason it's a pointer is for consistency with all the other literal fields.
Help - line wrap
In my code I have a multiple line summary (comments) for my main method.
when I run my executable and ask for help myapp.exe --help the summary gets line wrapped.
I would like for each line in my summary to have a new line between.
I have tried every mechanism to make this work to no joy (also looked in the dragonfruit code a little) but couldn't find a quick fix.
/// <summary>
It’d be super nice if libarchive aka libCVE had proper, human-readable changelogs with references to security fixes. Right now the NEWS file is so incomplete as to be useless, and the release notes page on the wiki hasn’t been updated in ages.
It'd be good to state publicly the oldest kernel and glibc (or even other libc versions) we support.
This would allow us to remove some legacy code or force support for legacy code.
This shouldn't require test to be functional (e.g. for some cases like module drivers it could be hard),
but LTP to be compiled and when difficult/impossible to achieve this functionality, it could resulted in TCO
Issue type
- Defect - Unexpected behaviour (obvious or verified by project member).
Defect
How to reproduce the issue
When querying a non-cached group membership by name, debug output states that the object the user is a member of was the parent of the group object.
if (&LDAP-Group == 'my-group') {
# success
}
Will emit a debug message similar to `ou=groups,dc=e
Printable format
Is there any chance that you will create a printable version of this docs as it would be very useful if it is distributed on my college tech club and my fellow linux geekmate. Thanks
Not sure if it's worth adding to the documentation but I found I had to add the following to the end of the fstab command otherwise the system would not boot cleanly.
,x-systemd.mount-timeout=30,_netdev
The line in fstab now looks like
mfsmount /mnt/mymnt fuse mfssubfolder=mydir,allow_other,x-systemd.mount-timeout=30,_netdev
I think it was trying to mount mooseFS before it had fini
I don't want to use current chunks loop for replication (mostly because is still unclear how it works).
What I would like is to set our cluster to replicate as much chunks as possible up to REPLICATION_BANDWIDTH_LIMIT_KBPS
What should I have to set and how ? I think that both REPLICATION_BANDWIDTH_LIMIT_KBPS and chunks loop limits are honored, so I have to set chunk loop to very high value
I'm packaging modernish for FreeBSD now. Usually, we put examples under share/examples/name, documentation under share/doc/name and any other data, that do not belong to any of the aforementioned directories, into share/name.
I wonder if you'd like to follow the same convention in this repository.
The reason is that I am not sure if I should move modernish examples to a standard pla
-
Updated
Jun 16, 2020 - Shell
Implement some test cases for standard memset()
-
Updated
Jun 2, 2020 - C
Is your feature request related to a problem? Please describe.
We don’t have anything in our code of conduct about how contributions are licensed and how we handle bad contributions or contributors. We should be explicit about that.
Describe the solution you'd like
A policy like Wikipedia’s about code.
Describe alternatives you've considered
N/A
Additional context
N/A
In the documentation at https://luaposix.github.io/luaposix/modules/posix.poll.html#rpoll the text of the link has the correct url, but the link target is just the page itself. I guess you need to put it in twice at
https://github.com/luaposix/luaposix/blob/master/ext/posix/poll.c#L246
We have a few branches in fs.writeFile that aren't being tested: https://codecov.io/gh/filerjs/filer/src/master/src/filesystem/implementation.js#L1850. To fix this, we need a few more tests added:
- test that passes invalid flags to
options.flags(i.e., doesn't includew) - test that passes a
numberfor thedataargument to write, and expects to have it written as a string.
-
Updated
Apr 17, 2020 - C
-
Updated
May 7, 2020 - Shell
Hi,
I'm trying to tackle the (frankly glaring) lack of any repair-enabled UDF fsck under macOS, by (shallow) porting of the still beta (and to-be-merged upstream) fsck, as part of (Linux) udftools (pali/udftools#13).
You can find more details here:
[https://github.com/argorain/udftools/pull/1](https://github.com/argor
The posted installation steps for manually installing the CloudABI toolchain with the cloudabi-run utility in Debian/Ubuntu, omits some important requirements:
- yaml2argdata headers need to be installed.
- arpc needs to be installed.
- The libyaml-cpp-dev package needs to be installed.
- python3 needs to be installed.
- pypeg2 needs to be installed.
- e
-
Updated
May 4, 2020 - Python
Improve this page
Add a description, image, and links to the posix topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the posix topic, visit your repo's landing page and select "manage topics."
It would be good if the docs and
--helpoutput could mention thatnvm installinstalls and uses the given Node version. I've probably wasted hours typingnvm install __ && nvm use __, - just discovered the second part has been unnecessary since this was fixed in 2014 :)