search for: fhs

Hi, I''m a new puppet user (thanks !) and I''m just looking at moving my homegrown manifest structure into something resembling the best practise guide at : http://www.reductivelabs.com/trac/puppet/wiki/PuppetBestPractice. It seems as if the structure here doesn''t map to the default puppet layout (and thus doesn''t work with the standard puppet config

On 10/04/2017 04:54 AM, Mark Haney wrote: > Why is it so hard for people to understand that var/run IS NOT > PERSISTENT and was never meant to be?? Do they not teach basic Unix > concepts anymore? http://www.pathname.com/fhs/pub/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA While FHS notes that *files* should be cleared during the boot process, it does not indicate that directories should be, and that is the source of this problem.? Packages on recent Fedora, RHEL, or CentOS releases should use tmpfiles.d to define direct...

Hello, I'm working on a CD-distro and I'm using isolinux bootloader (of course :-) ). But I also want to respect FHS... so my question is: can I put isolinux binary, cfg files etc. in /boot dir instead of /isolinux? Well, I could try, but... I'm not using my work-PC now. TIA, aded PS: sorry for my English.

...hon3.7/site-packages/samba/samdb.py", line 458, in newuser ??? dnsdomain = ldb.Dn(self, self.domain_dn()).canonical_str().replace("/", "") How do I fix this? Everthing is using the default path (/usr/local/samba). The only paramater I passed to configure was --enable-fhs since I remember that it croaks without that. So I just did: ./configure --enable-fhs make && make install I tried looking for this online, but while I've seen this error online, it's always something that doesn't list the fix. Either they say "oh, never mind, I got it&q...

...user >> ??? dnsdomain = ldb.Dn(self, >> self.domain_dn()).canonical_str().replace("/", "") >> >> >> How do I fix this? Everthing is using the default path >> (/usr/local/samba). The only paramater I passed to configure was >> --enable-fhs since I remember that it croaks without that. > It shouldn't 'croak' without '--enable-fhs' I did some experimenting and it seems that configure dies if you use --prefix=/usr or --prefix=/usr/local and don't use --enable-fhs. Here's what it said: Don't install...

...10.2017 um 17:54 schrieb Jonathan Billings: > I think that the important learning points today are: > > 1.) CentOS7 (and any other distro that uses systemd) will have /run as > a tmpfs filesystem, and /var/run points to /run on CentOS7, so even if > you think this disagrees with the FHS, that's the way it is for > CentOS. And fun fact: not only RHEL 7 and thus CentOS 7 does so, but too Debian 9 and Ubuntu 16.04 LTS (I have no newer test install of that distro). And frankly speaking, I don't see any indication that this violates with the FHS and that /var/run must pe...

hi all, as i heard, i need winbind to connect linux-clients on samba. i installed this - without pam (in the hope this would work...) but this constellation seems to be needed, as i still cannot connect, even if winbind logs my domain as accepted. Do i really have to do the pam-configuration on the samba-server-side too?? i just thought, it was enough to authentificate against smbpasswd. is

...: 1) would you share your build notes with me (v. 4.10.0 on Ubuntu 18.04)? 2) do you have any insight re: the version expected to have the 'make test' fix (earlier question above directed to Andrew)? 3) can you provide any insights on pros/cons of configuring as default vs. configuring with fhs when building on Ubuntu 18.04? I note (a) with respect to default, your comment regarding Ubuntu still expecting some distro packages and (b) that you and Louis both seem to configure fhs. On the other hand, it seems that there is more to the fhs configuration, e.g. the "backport" require...

On 02/04/2023 08:05, Anderson Sampaio Mello via samba wrote: > Thanks for the answer. > > The path for the two DCs is correct yes, and yes I compiled it for the two > DC servers like this: > > ./configure --with-systemd --prefix=/usr/local/samba --enable-fhs And that is possibly your problem: --with-systemd is the default if the systemd libs are installed --prefix=/usr/local/samba is the default --enable-fhs is possibly a good idea, but only if you had gone on to add things like '--prefix=/usr --sysconfdir=/etc --localstatedir=/var' > m...

...t; On 02/04/2023 08:05, Anderson Sampaio Mello via samba wrote: >> Thanks for the answer. >> >> The path for the two DCs is correct yes, and yes I compiled it for the two >> DC servers like this: >> >> ./configure --with-systemd --prefix=/usr/local/samba --enable-fhs > > And that is possibly your problem: > --with-systemd is the default if the systemd libs are installed > > --prefix=/usr/local/samba is the default > > --enable-fhs is possibly a good idea, but only if you had gone on to add things like '--prefix=/usr --sysconfdir=/etc...

...e than mine, but I don't really understand why you require this. It is really meant to ensure that the developers don't break things, it isn't required to run Samba in production. > 3) > can you provide any insights on pros/cons of configuring as default > vs. configuring with fhs when building on Ubuntu 18.04? I note (a) > with respect to default, your comment regarding Ubuntu still > expecting some distro packages and (b) that you and Louis both seem > to configure fhs. On the other hand, it seems that there is more to > the fhs configuration, e.g. the "ba...

...and will never conflict with or replace packages in the base Enterprise Linux distributions." If there wasn?t some sort of conflict, then there wouldn?t be an issue with lighttpd. Mariadb is from the mariadb repo. It is quite obvious that Centos causes issues because it is not following the FHS. [1]: http://fedoraproject.org/wiki/EPEL > If you refuse to do as best practices insist (and have for nearly HALF I?m not insisting on anything, I?m merely pissed that things are broken. It has turned out that this is due to the way Centos doesn?t follow the FHS. Not following the FHS proba...

Hello, I just attempted to remove both the ypbind and the yp-tools packages using the package parameter with yum. As it turns out, both of these packages depend on each other. Is there a way of forcing package removal and, if there is not, is there a way of making all packages to be removed be collapsed into the same yum command? Either of these solutions would solve the problem with the

...me - who started with Sernet's packages and then switched to compiled version there is an option from ./configure script called "--enable-fhd" which is meant to install Samba DB and stuffs into /var/lib/samba as with Sernet's packages. >From configure's help: --enable-fhs Use FHS-compliant paths (default no) You should consider using this together with: --prefix=/usr --sysconfdir=/etc --localstatedir=/var So the configure line become: ./configure --enable-fhs --prefix=/usr --sysconfdir=/etc --localstatedir=/var + Your own options...

I'm starting to prepare the next release. Since 0.8.3 I've made a number of changes to get working builds working on HPUX and OSF, and made some of the Windows specific bits more robust. I'd like to check that these haven't broken CYGWIN or IRIX builds, but I don't have access to these platforms. If you are able to test, it'd be most appreciated if you could. Download a

On 02/04/2023 09:21, Michael Tokarev via samba wrote: > Neither of the 3 should be a problem. Especially the ones which > are already set by default.? --enable-fhs uses slightly different > layout within $prefix, that's all. The build-time configuration > looks entirely okay. You may be correct Michael, but I still wouldn't use '--enable-fhs' by itself. > > There's something else going on here. Very probaby. > > An...

>>> When building Samba 4.4.0rc and then doing an install to >>> /usr/local/samba, a directory "libexec" is being created which then >>> contains a "samba" directory with a single "smbspool_krb5_wrapper" >>> file inside (/usr/local/samba/libexec/samba/ >>> smbspool_krb5_wrapper). This is not very clean, is it? >>>

Thanks for the answer. The path for the two DCs is correct yes, and yes I compiled it for the two DC servers like this: ./configure --with-systemd --prefix=/usr/local/samba --enable-fhs make up make install After the domain was created, sysvol was created here: /usr/local/samba/var/lib/samba/sysvol And the new DC also created sysvol in the same location. But why samba-tool ntacl sysvolreset cannot restore permissions and these BUFFER messages appear? Em dom., 2 de abr. de 202...

...oint. > > If Unix systems didn't insist upon scattering files all the hell over > /etc, /usr/local/bin, /usr/local/lib, /usr/local/include, > /var/share/mybunghole, /opt/local/stupidlib, etc. etc... Anyone interested in _why_ un*x systems use this structure, take a look at the FHS (Filesystem Hierarchy Standard) project at http://www.pathname.com/fhs/ A lot of it has to do with managing networks of machines in a professional environment, which is why it seems pointless to a single workstation installation for a home user. However it does help to understand that there a...

On Tuesday 03 October 2017 18:24:01 Mark Haney wrote: > What issue? That the PID is dropped on reboot?? What else are you > putting in there?? I'm beginning to question whether you know what > you're doing or not.? Lighttpd doesn't store any persistent info in > /var/run/ because, like everything else, /var/run isn't for persistent > data. Mark, Many Non-Centos