similar to: Issues accessing ZFS-shares on Linux

I added one testshare /home/testijako and connected to it with the same credentials as I would connect to ZFS-shares. Then I did the strace to that particular PID and tried connecting to one ZFS-share. There was indeed an error which might have something to do with this issue: Line 2001: lstat("/tank/rex", 0x7fff1f6fb2c0) = -1 ENOENT (No such file or directory) Im sure that folder

On Mon, Jan 08, 2018 at 11:06:37PM +0200, John Doe via samba wrote: > Hi, > > I am having a really strange problem with my Samba shares on Debian > Buster. None of the users can access any shares, which reside on > ZFS-filesystem. Any other share works just fine. For example, if I > create a normal folder to /home with same permissions and replace a > ZFS-share with that, it

I just noticed that by running by commands /usr/sbin/smbd -D or /usr/sbin/smbd -i without systemd's unit, all shares work perfectly so the problem must then be somehow related to systemd.. Let the testing continue.. I also tested what happens if I comment out everything and just use ExecStart=/usr/sbin/smbd -D as that command worked on the console. That did not help. For the record, this is

I think it may have something to do with my disks being encrypted. This issue happened after updating systemd to version 236, ZoL to 0.7.4 and kernel to 4.14. I have always mounted the pool manually by first opening LUKS-encrypted disks and after that issuing zpool import tank. Is there any way to still use systemd to manage smbd or do I have to just always start it manually? This is how the

Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex InternalErrorException.reportBug.Rex Package.Rex Person.Rex Rdoc.Rex setMethodS3.Rex StaticFields.Rex when running R CMD build in R v2.3.0 devel. I do understand what is going on. In my *.R files I keep so called Rdoc

Hello, I tried lunch something but the anwer was "can't find apps" (I used absolute path too) [serge@rex wineserver-rex]$ wine /windows/ProgramFiles/Office/winword.exe Invoking /opt/wine/bin/wine.bin /windows/ProgramFiles/Office/winword.exe ... Wine failed with return code 2 /usr/bin/wine: line 516: 1046 Compl?t? tail -f $log_name Deleting /tmp/wine.log.Vv4t6C

On Wed, Dec 24, 2014 at 2:43 PM, Craig Topper <craig.topper at gmail.com> wrote: > I believe this particular error is caused by this. That seems easy enough > to just drop the bit. Do you have other non-mmx examples? > > case TYPE_MM: \ > if (index > 7) \ > *valid = 0;

Greetings, The following question has come up in an off-list discussion. Is it possible to construct a regular expression 'rex' out of two given regular expressions 'rex1' and 'rex2', such that a character string X matches 'rex' if and only if X matches 'rex1' AND X does not match 'rex2'? The desired end result can be achieved by logically combining

Create an object hierarchy to represent different bootloaders for Linux guests, moving the separate handling of grub1 and grub2 in different classes: this isolates the code for each type of bootloader together, instead of scattering it all around. This is mostly code refactoring, with no actual behaviour change. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 2 + v2v/bootloaders.ml

hi, i think the current X86 disassembler is quite broken and fails badly on handling REX for x86_64 code. below are some examples: $ echo "0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0 $ echo "0x40,0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0 $ echo

Tracking down a problem with one of our benchmark codes, we've discovered that some of the patterns in X86InstrX86-64.td are wrong. Specifically: def MOV64toPQIrm : RPDI<0x6E, MRMSrcMem, (outs VR128:$dst), (ins i64mem:$src), "mov{d|q}\t{$src, $dst|$dst, $src}", [(set VR128:$dst, (v2i64 (scalar_to_vector

Tabs should not be doubly-escaped in regexp. Signed-off-by: Shahar Lev <shahar@stratoscale.com> --- v2v/convert_linux.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index adbcaa2..1e9e689 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -581,7 +581,7 @@ let rec convert ~keep_serial_console (g : G.guestfs)

On 26/10/2019 22:51, tootifrooti via samba wrote: >> Is there any way to still use systemd to manage smbd or do I have to >> just always start it manually? > Did you ever find a solution to this problem? I'm experiencing a very > similar problem right now. When running samba via systemd any access to a > share on a zfs filesystem results in the `make_connection_snum: >

1. AWS the name tag is not mandatory - using default as a name 2. AWD doesn't prefix 'ovf:' as prefix to disk path There is an open bug for oVirt: https://bugzilla.redhat.com/show_bug.cgi?id=1371843 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/input_ova.ml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/v2v/input_ova.ml

Try to improve the way packages of VMware tools are removed from YUM-based guests: - when filtering the package itself from its providers, do a stricter check so either the provide is the unversioned package, or it is exactly its own name - if the package has no other providers, then going further will cause the invocation of 'yum install' with no packages, and thus the package

1. AWS the name tag is not mandatory - using default as a name 2. AWD doesn't prefix 'ovf:' as prefix to disk path There is an open bug for oVirt: https://bugzilla.redhat.com/show_bug.cgi?id=1371843 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/input_ova.ml | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/v2v/input_ova.ml

The OVF standard allows the use of SHA256 hashes in the manifest file. Adding support for this. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 513fe30..5420c85 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -133,7 +133,7

Hi, Intel's Xed can interpret "43 40 04 75" as "add al, 0x75", but LLVM's X86 disassembler considers this invalid code. I guess the reason is that LLVM fails to recognize the REX prefix in this case. Is this correct? Thanks. Jun -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I just started using R and am having trouble with the below error: I type: > df <- read.csv("/home/rex/Desktop/mytable.csv") which gives me what I want: ... 639 2006-05-26 16:46:54 4 16 640 2006-05-26 17:05:36 5 17 641 2006-05-26 17:30:48 6 17 But now I try: > plot(df[4],df[3]) Error in pmatch(x, table, duplicates.ok) : argument is not of

Dudes and/or Dudettes: HEEELLLPPP! (such a newbie statement) I can't get my remote SMB mounts to work on my Linux box. duke was happily running Slackware Linux 2.0.36 and Samba 1.9.18p8 . I upgraded to Linux 2.2.0pre9 (2.2.0final), which seemed to require upgrading to Samba 2.0.0 . (I don't remember the exact errors) Now i can't get my NT and '95 disks to stay mounted on