Displaying 2 results from an estimated 2 matches for "windows&linux".
2017 Jan 17
3
O_CLOEXEC-like functionality for llvm::raw_fd_ostream
...g for me to be able to do that is the ability to open a file
with the O_CLOEXEC flag (to prevent us leaking file descriptors into
the debugged process).
So I tried adding a F_NonInheritable flag to the raw_fd_ostream
constructor, which would map to O_CLOEXEC on unix, and non-inheritable
handles on windows. However, I encountered a discrepancy in the
current behavior there.
The current behavior on unix is to make the file descriptors
inheritable (as that is the platform default). On windows, the current
behavior is to make the handles *non*-inheritable (again, because of
platform default). Obviously...
2008 Oct 28
1
The way things used to work...
...translated in my attempt to make things go my way,
rather than (someone might call it) right way.
Since I work as sysadmin, surrounded with mostly computer illiterate users, my
primary goal is to make things effortless to them... (brainless is better
word...), and since it is mixed environment (windows&linux), and of course all
they ever saw before is windows.... you can understand a nature of limitations
that are in front of me.
It took me some time (again trial and error) to compile set of rules for
smb.conf that makes things exactly as I want. Efficient and nice.
This smb.conf is worki...