Re: du Weirdness - how is this possible

On 03/13/2018 01:19 PM, Stephen Morris wrote: It just seems counter intuitive to me to have to issue another command (even if one knows of its existence) to get a command to function "properly". Having read this thread, I think you may still not grasp what the shell does and what command

[389-users] Re: autosizing the cache

Hi William, With autosizing on I configured the changelog backend: dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config cn: changelog objectClass: top objectClass: extensibleObject objectClass: nsBackendInstance nsslapd-suffix: cn=changelog nsslapd-cachesize: -1 nsslapd-cachememsize:

[389-users] Re: autosizing the cache

On Tue, 2018-03-13 at 13:05 -0500, Sergei Gerasenko wrote: > Sorry to resurrect this thread, but I’ve upgraded to 1.3.6 and so my > question is back on the table :) > > My cn=userRoot,cn=ldbm database,cn=plugins,cn=config is currently: > > ... > nsslapd-cachesize: -1 > nsslapd-cachememsize:

Re: du Weirdness - how is this possible

On 03/14/18 08:20, jdow wrote: > "ls .?*" is another "ls -A" equivalent. Hummm.   Not really?   Since .. is matched and depending on where you are in the file system you may encounter this [egreshko@meimei test-dir]$ ls -A .hidden  stuff  test  test1  test2 [egreshko@meimei test-dir]$

[389-users] Re: Admin Gateway over https

On Tue, 2018-03-13 at 10:55 +1000, William Brown wrote: > On Thu, 2018-03-08 at 05:26 +, Eric Wheeler wrote: > > Thanks for the confirmation regarding secure connections and the > > clarification regarding dsgw. I will focus on other alternatives. I > > would be interested in exploring cli

Re: du Weirdness - how is this possible

howing. (Isn't "ls -l" simpler? I alias that to "ll" and "lla" is "ls -lA". This thread is amusing and bemusing for the willful disregard for standard 'ix behavior since virtually the beginning of 'ix time. {^_-} On 20180313 16:28, Ed Greshko wrote

Re: du Weirdness - how is this possible

On 03/13/2018 04:59 PM, Rick Stevens wrote: > On 03/13/2018 02:21 PM, Stephen Morris wrote: >> On 13/3/18 8:46 pm, Patrick O'Callaghan wrote: >>> On Mon, 2018-03-12 at 18:25 -0700, Rick Stevens wrote: On 03/12/2018 03:37 PM, Patrick O'Callaghan wrote: > On Tue, 2018-03-13 at 07:26 +1100,

Re: du Weirdness - how is this possible

On 03/13/2018 02:21 PM, Stephen Morris wrote: > On 13/3/18 8:46 pm, Patrick O'Callaghan wrote: >> On Mon, 2018-03-12 at 18:25 -0700, Rick Stevens wrote: >>> On 03/12/2018 03:37 PM, Patrick O'Callaghan wrote: On Tue, 2018-03-13 at 07:26 +1100, Stephen Morris wrote: >> 'du' with no

Re: du Weirdness - how is this possible

On 03/13/2018 01:44 PM, Stephen Morris wrote: > On 14/3/18 7:19 am, Stephen Morris wrote: >> On 13/3/18 9:05 am, Ed Greshko wrote: >>> On 03/13/18 05:47, Ed Greshko wrote: On 03/13/18 05:20, Stephen Morris wrote: > Thanks Ed, I'll check the doco out, I was just expecting the > command

Re: du Weirdness - how is this possible

On 03/14/18 05:22, Ed Greshko wrote: > The later command is basically creating a list of files (a shell function) > and doing > a "du" on each file individually. Here is another example to show you what is happening [egreshko@meimei test-dir]$ ls stuff  test  test1  test2 [egreshko@meimei

[389-users] Re: repl-monitor.pl

On 03/13/2018 06:00 PM, Sergei Gerasenko wrote: >> Is this a winsync replication agreement? If so, the lag time can not be >> determined if I am correct. > No, it’s all Linux servers. Not sure what winsync is. Me neither sometimes ;-) > >> This information is all determined from the replication

Re: du Weirdness - how is this possible

On Wed, 2018-03-14 at 08:21 +1100, Stephen Morris wrote: > What I hadn't realized until Patrick mentioned it, was the significance > of the * in the path specification. I hadn't realized that with using > the * not only did it cause files prefixed with a '.' to be ignored but > it also causes

[389-users] Re: repl-monitor.pl

> Is this a winsync replication agreement? If so, the lag time can not be > determined if I am correct. No, it’s all Linux servers. Not sure what winsync is. > This information is all determined from the replication agreement. Are > all the servers using the same version of 389-ds-base?

[389-users] Re: repl-monitor.pl

On 03/13/2018 05:07 PM, Sergei Gerasenko wrote: > Hi all, > > I think this is more a question for Mark since he wrote repl-monitor :) > > I built a new node and promoted it to be a domain/ca replica. Is this a winsync replication agreement?  If so, the lag time can not be determined if I am

Re: du Weirdness - how is this possible

On 03/14/18 04:44, Stephen Morris wrote: > > I'm now completely confused. The command du -abh /home/steve/workspace is now > displaying the information directories beginning with a '.' and at least some > files > beginning with a '.' without having issued the shopt command. The command you're

Re: du Weirdness - how is this possible

On 13/3/18 8:46 pm, Patrick O'Callaghan wrote: On Mon, 2018-03-12 at 18:25 -0700, Rick Stevens wrote: On 03/12/2018 03:37 PM, Patrick O'Callaghan wrote: On Tue, 2018-03-13 at 07:26 +1100, Stephen Morris wrote: 'du' with no parameters recursively lists all the subdirectories and their sizes,

[389-users] repl-monitor.pl

Hi all, I think this is more a question for Mark since he wrote repl-monitor :) I built a new node and promoted it to be a domain/ca replica. Everything seems to be working fine *except* repl-monitor.pl has ?:??:?? in the lag column for the CA segment from the pre-existing CA master to the new

Re: du Weirdness - how is this possible

On 14/3/18 7:42 am, Rick Stevens wrote: On 03/13/2018 01:19 PM, Stephen Morris wrote: On 13/3/18 9:05 am, Ed Greshko wrote: On 03/13/18 05:47, Ed Greshko wrote: On 03/13/18 05:20, Stephen Morris wrote: Thanks Ed, I'll check the doco out, I was just expecting the command to do exactly what

Re: du Weirdness - how is this possible

On 13/3/18 9:33 am, Robert Nichols wrote: On 03/12/2018 03:26 PM, Stephen Morris wrote: Thanks Patrick, taking this a step further, it seems to me that the only parameter for du that, to me, provides the correct file size is -b as shown below. I am listing my Desktop directory via ll, du -hs

Re: du Weirdness - how is this possible

On 14/3/18 7:19 am, Stephen Morris wrote: On 13/3/18 9:05 am, Ed Greshko wrote: On 03/13/18 05:47, Ed Greshko wrote: On 03/13/18 05:20, Stephen Morris wrote: Thanks Ed, I'll check the doco out, I was just expecting the command to do exactly what the help info said, output the information for

Re: du Weirdness - how is this possible

On 03/13/2018 01:19 PM, Stephen Morris wrote: > On 13/3/18 9:05 am, Ed Greshko wrote: >> On 03/13/18 05:47, Ed Greshko wrote: >>> On 03/13/18 05:20, Stephen Morris wrote: Thanks Ed, I'll check the doco out, I was just expecting the command to do exactly what the help info said,

Re: du Weirdness - how is this possible

On 13/3/18 9:05 am, Ed Greshko wrote: On 03/13/18 05:47, Ed Greshko wrote: On 03/13/18 05:20, Stephen Morris wrote: Thanks Ed, I'll check the doco out, I was just expecting the command to do exactly what the help info said, output the information for all files, not just a subset. It *does*

Re: Troubleshooting random hangs

Hi Suvayu, On Mon, 5 Mar 2018 at 16:23 Suvayu Ali wrote: > Hi, > > I have been having random hangs on my new Ryzen workstation (Ryzen 5 > 2400G + B350 mobo). My hardware is supposedly properly supported on > 4.15+ kernels. But I have been unable to boot with any

[389-users] Re: autosizing the cache

Sorry to resurrect this thread, but I’ve upgraded to 1.3.6 and so my question is back on the table :) My cn=userRoot,cn=ldbm database,cn=plugins,cn=config is currently: ... nsslapd-cachesize: -1 nsslapd-cachememsize: 1543503872 nsslapd-readonly: off nsslapd-require-index: off

Re: PHP SOAP error after upgrade

On 03/13/2018 02:14 AM, Bill Shirley wrote: > You've posted very little code.  Have you tried looking at the > headers?  You > must turn on trace: >   $soap_options = array( >     'trace'=>true >     // ,'soap_version'=>SOAP_1_2 >     // ,'exceptions'=>false >     // ,'classmap'=>$classmap >  

Re: SELinux is blocking lightdm login to Xfce

On 03/12/2018 11:53 PM, Ed Greshko wrote: There are times where you will have selinux preventing something but you won't get an AVC in the audit.log.  This due to a policy which has "dontaudit" enabled.   If you run into this situation again you should try the command "semodule -BD"  The D

Re: SELinux is blocking lightdm login to Xfce

On 03/13/2018 02:39 AM, Lukas Vrabec wrote: On 03/13/2018 06:57 AM, ToddAndMargo wrote: Follow up: With everyone's help, I cleaned up my SELinux homedir's and set Samba's SELinux stuff right. I still could not log in from lightdm, except to root, when SLElinux was Enforcing. And SEAlert was

Re: du Weirdness - how is this possible

On Mon, 2018-03-12 at 18:25 -0700, Rick Stevens wrote: > On 03/12/2018 03:37 PM, Patrick O'Callaghan wrote: > > On Tue, 2018-03-13 at 07:26 +1100, Stephen Morris wrote: > > > > 'du' with no parameters recursively lists all the subdirectories and > > > > their sizes, along with the grand total.

Re: SELinux is blocking lightdm login to Xfce

On 03/13/2018 06:57 AM, ToddAndMargo wrote: > Follow up: > > With everyone's help, I cleaned up my SELinux homedir's > and set Samba's SELinux stuff right. > > I still could not log in from lightdm, except to root, > when SLElinux was Enforcing. > > And SEAlert was completely quiet.  And >

Re: How do you reset Selinux back to default?

On 03/13/2018 07:53 AM, Samuel Sieb wrote: > On 03/12/2018 06:28 PM, ToddAndMargo wrote: >> I mean before I started adding things to SELinux based on >> SEAlerts and such.  In other word, set SELinux back to >> the way I found it after I installed Linux > > I thought I had seen something to list

Re: SELinux is blocking lightdm login to Xfce

On 03/13/18 13:57, ToddAndMargo wrote: > Thank you all for the tips.  I wrote down about five of them, > so I would not forget.  SELinux baffles me at times. Good to hear all is working now. One thing I just realized I was remiss in mentioning.  There are times where you will have selinux

Re: How do you reset Selinux back to default?

On 03/12/2018 06:28 PM, ToddAndMargo wrote: I mean before I started adding things to SELinux based on SEAlerts and such.  In other word, set SELinux back to the way I found it after I installed Linux I thought I had seen something to list changed modules, but now I think I misunderstood. I

Re: PHP SOAP error after upgrade

You've posted very little code.  Have you tried looking at the headers?  You must turn on trace:   $soap_options = array(     'trace'=>true     // ,'soap_version'=>SOAP_1_2     // ,'exceptions'=>false     // ,'classmap'=>$classmap   );   $soap_client = new SoapClient($wsdl_url, $soap_options);