search for: ws

I'm noticing some differences between making an explicit call to windows() to generate a graphics device and going with whatever R gives you when you just start plotting, which raises the question of just what the nature of the default device is. I've had a hard time researching this so far, so I'm asking the list. Here are two code snippets: ################...

I have a following problem: The call qplot(wg, v.realtime, data=df.best.medians$gv1, colour=sp, geom="boxplot") works nice: for each value of the wg factor I get two box-plots (two levels in the sp factor) in different colours, side-by-side, centered at the wg x-axis. However, I want to separate the data belonging to different levels of the n factor, so I add the facets option:

...n servers glusterfs2 and glusterfs3 again. [root at glusterfs2 Log_Files]# gluster volume info Volume Name: StoragePool Type: Distributed-Disperse Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f Status: Started Number of Bricks: 20 x (2 + 1) = 60 Transport-type: tcp Bricks: Brick1: glusterfs1sds:/ws/disk1/ws_brick Brick2: glusterfs2sds:/ws/disk1/ws_brick Brick3: glusterfs3sds:/ws/disk1/ws_brick Brick4: glusterfs1sds:/ws/disk2/ws_brick Brick5: glusterfs2sds:/ws/disk2/ws_brick Brick6: glusterfs3sds:/ws/disk2/ws_brick Brick7: glusterfs1sds:/ws/disk3/ws_brick Brick8: glusterfs2sds:/ws/disk3/ws_bri...

...e info > > > > Volume Name: StoragePool > > Type: Distributed-Disperse > > Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f > > Status: Started > > Number of Bricks: 20 x (2 + 1) = 60 > > Transport-type: tcp > > Bricks: > > Brick1: glusterfs1sds:/ws/disk1/ws_brick > > Brick2: glusterfs2sds:/ws/disk1/ws_brick > > Brick3: glusterfs3sds:/ws/disk1/ws_brick > > Brick4: glusterfs1sds:/ws/disk2/ws_brick > > Brick5: glusterfs2sds:/ws/disk2/ws_brick > > Brick6: glusterfs3sds:/ws/disk2/ws_brick > > Brick7: glusterfs1s...

On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > 3.7.19 > These are the only callers for removexattr and only _posix_remove_xattr has the potential to do removexattr as posix_removexattr already makes sure that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr happens only from healing code of afr/ec. And this can only happen

...> >> Type: Distributed-Disperse >> >> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f >> >> Status: Started >> >> Number of Bricks: 20 x (2 + 1) = 60 >> >> Transport-type: tcp >> >> Bricks: >> >> Brick1: glusterfs1sds:/ws/disk1/ws_brick >> >> Brick2: glusterfs2sds:/ws/disk1/ws_brick >> >> Brick3: glusterfs3sds:/ws/disk1/ws_brick >> >> Brick4: glusterfs1sds:/ws/disk2/ws_brick >> >> Brick5: glusterfs2sds:/ws/disk2/ws_brick >> >> Brick6: glusterfs3sds:/ws/disk...

...) install glusterfs-debuginfo 3) change the path of the translator in the systemtap script to appropriate values for your system (change "/usr/lib64/glusterfs/3.12dev/xlator/protocol/client.so" and "/usr/lib64/glusterfs/3.12dev/xlator/storage/posix.so") 4) run the script as follows #stap -v fop_trace.stp The o/p would look like these .. additionally arguments will also be dumped if glusterfs-debuginfo is also installed (i had not done it here.) pid-958: 0 glusterfsd(3893):->posix_setxattr pid-958: 47 glusterfsd(3893):<-posix_setxattr pid-966: 0 glusterfsd(50...

...info > 3) change the path of the translator in the systemtap script to > appropriate values for your system > (change "/usr/lib64/glusterfs/3.12dev/xlator/protocol/client.so" and > "/usr/lib64/glusterfs/3.12dev/xlator/storage/posix.so") > 4) run the script as follows > #stap -v fop_trace.stp > > The o/p would look like these .. additionally arguments will also be > dumped if glusterfs-debuginfo is also installed (i had not done it here.) > pid-958: 0 glusterfsd(3893):->posix_setxattr > pid-958: 47 glusterfsd(3893):<-posix_setxattr...

...) install glusterfs-debuginfo 3) change the path of the translator in the systemtap script to appropriate values for your system (change "/usr/lib64/glusterfs/3.12dev/xlator/protocol/client.so" and "/usr/lib64/glusterfs/3.12dev/xlator/storage/posix.so") 4) run the script as follows #stap -v fop_trace.stp The o/p would look like these .. additionally arguments will also be dumped if glusterfs-debuginfo is also installed (i had not done it here.) pid-958: 0 glusterfsd(3893):->posix_setxattr pid-958: 47 glusterfsd(3893):<-posix_setxattr pid-966: 0 glusterfsd(50...

...3) change the path of the translator in the systemtap script to > appropriate values for your system > > (change "/usr/lib64/glusterfs/3.12dev/xlator/protocol/client.so" and > "/usr/lib64/glusterfs/3.12dev/xlator/storage/posix.so") > > 4) run the script as follows > > #stap -v fop_trace.stp > > The o/p would look like these .. additionally arguments will also be > dumped if glusterfs-debuginfo is also installed (i had not done it here.) > pid-958: 0 glusterfsd(3893):->posix_setxattr > pid-958: 47 glusterfsd(3893):<-posix_set...

...t of which sub-volumes in case of disperse volume, for example in below volume has two sub-volumes : Type: Distributed-Disperse Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b Status: Started Snapshot Count: 0 Number of Bricks: 2 x (4 + 2) = 12 Transport-type: tcp Bricks: Brick1: pdchyperscale1sds:/ws/disk1/ws_brick Brick2: pdchyperscale2sds:/ws/disk1/ws_brick Brick3: pdchyperscale3sds:/ws/disk1/ws_brick Brick4: pdchyperscale1sds:/ws/disk2/ws_brick Brick5: pdchyperscale2sds:/ws/disk2/ws_brick Brick6: pdchyperscale3sds:/ws/disk2/ws_brick Brick7: pdchyperscale1sds:/ws/disk3/ws_brick Brick8: pdchyp...

Hello $LIST, i setup a new clean domain to examine the feature of updating/creating PTR records. When i call ipconfig /registerdns on the client i get this entry in the windows eventlog (sorry german) Fehler beim Registrieren der Hostressourceneinträge (A oder AAAA) für den Netzwerkadapter mit den folgenden Einstellungen: Adaptername: {2A467E48-624B-4CCF-9B7D-9BA5629D8117} Hostname: w7test Primäres Domänensuffix: samba.laurenz.ws DNS-Serverliste:...

...ng the init.el: (setq bell-volume 0) (setq sound-alist nil) (setq grep-find-use-xargs nil) (require 'ess-site) I get the following error: (1) (initialization/error) An error has occurred while loading $home/.xemacs/init.el: Cannot open load file: "ess-site" Backtrace follows: signal(file-error ("Cannot open load file" "ess-site")) # bind (path handler filename nosuffix nomessage noerror file) load("ess-site" nil require nil) # (unwind-protect ...) require(ess-site) ... The above init.el worked for earlier versions of Xema...

HI, i just played around with Windows 2008 R2 as ADS Server and two SAMBA 4 as additional DCs. Setting up the Samba 4 DCs works fine. Now I wanted to remove the last Windows DC with dcpromo. It fails with the following statement: Der Vorgang konnte nicht durchgef?hrt werden. Fehler: Active Directory konnte keinen anderen Dom?...

...administrator Password for [SAMBA\administrator]: > INFO 2023-11-20 15:30:05,639 pid:73781 > /usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA > INFO 2023-11-20 15:30:05,640 pid:73781 > /usr/lib/python3/dist-packages/samba/join.py #1617: realm is > samba.laurenz.ws > Calling bare provision > INFO 2023-11-20 15:30:05,711 pid:73781 > /usr/lib/python3/dist-packages/samba/provision/__init__.py #2108: > Looking up IPv4 addresses > INFO 2023-11-20 15:30:05,712 pid:73781 > /usr/lib/python3/dist-packages/samba/provision/__init__.py #2125: > Looki...

...mba_dom/$(hostname -d) -U administrator Password for [SAMBA\administrator]: INFO 2023-11-20 15:30:05,639 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA INFO 2023-11-20 15:30:05,640 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1617: realm is samba.laurenz.ws Calling bare provision INFO 2023-11-20 15:30:05,711 pid:73781 /usr/lib/python3/dist-packages/samba/provision/__init__.py #2108: Looking up IPv4 addresses INFO 2023-11-20 15:30:05,712 pid:73781 /usr/lib/python3/dist-packages/samba/provision/__init__.py #2125: Looking up IPv6 addresses WARNING 2023-1...

...as two sub-volumes : > > Type: Distributed-Disperse > > Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 2 x (4 + 2) = 12 > > Transport-type: tcp > > Bricks: > > Brick1: pdchyperscale1sds:/ws/disk1/ws_brick > > Brick2: pdchyperscale2sds:/ws/disk1/ws_brick > > Brick3: pdchyperscale3sds:/ws/disk1/ws_brick > > Brick4: pdchyperscale1sds:/ws/disk2/ws_brick > > Brick5: pdchyperscale2sds:/ws/disk2/ws_brick > > Brick6: pdchyperscale3sds:/ws/disk2/ws_brick > >...

...t of which sub-volumes in case of disperse volume, for example in below volume has two sub-volumes : Type: Distributed-Disperse Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b Status: Started Snapshot Count: 0 Number of Bricks: 2 x (4 + 2) = 12 Transport-type: tcp Bricks: Brick1: pdchyperscale1sds:/ws/disk1/ws_brick Brick2: pdchyperscale2sds:/ws/disk1/ws_brick Brick3: pdchyperscale3sds:/ws/disk1/ws_brick Brick4: pdchyperscale1sds:/ws/disk2/ws_brick Brick5: pdchyperscale2sds:/ws/disk2/ws_brick Brick6: pdchyperscale3sds:/ws/disk2/ws_brick Brick7: pdchyperscale1sds:/ws/disk3/ws_brick Brick8: pdchyp...

...--targetdir=/backup/linux/samba-dom Password for [SAMBA\administrator]: INFO 2020-05-05 20:46:57,256 pid:25729 /usr/lib/python3/dist-packages/samba/join.py #1574: workgroup is SAMBA INFO 2020-05-05 20:46:57,256 pid:25729 /usr/lib/python3/dist-packages/samba/join.py #1577: realm is samba.laurenz.ws Calling bare provision INFO 2020-05-05 20:46:57,320 pid:25729 /usr/lib/python3/dist-packages/samba/provision/__init__.py #2128: Looking up IPv4 addresses INFO 2020-05-05 20:46:57,325 pid:25729 /usr/lib/python3/dist-packages/samba/provision/__init__.py #2145: Looking up IPv6 addresses WARNING 20...

...ar/lib/samba/private/secrets Starting transaction on /var/lib/samba/private/sam.ldb backing up /var/lib/samba/private/sam.ldb copying locked/related file /var/lib/samba/private/sam.ldb.d/metadata.tdb backing up locked/related file /var/lib/samba/private/sam.ldb.d/DC=SAMBA,DC=LAURENZ,DC=WS.ldb backing up locked/related file /var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=SAMBA,DC=LAURENZ,DC=WS .ldb backing up locked/related file /var/lib/samba/private/sam.ldb.d/DC=FORESTDNSZONES,DC=SAMBA,DC=LAURENZ,DC=WS .ldb backing up locked/related file /var/lib/samba/private/sam...