similar to: Wait for interface to become available instead of dying?

Hello, everyone! I would like to solve the following problem. Btw, I''m terribly sorry about the pseudo-asciiart, but that''s all I can paint as a tropology. I''m hoping it''ll be enough. ----Internet---- | | | eth0 machine A routing+ipchains eth1 | ------------------ machine B So, given I''m running kernel 2.4.19 and using ipchains

Dear Free Audio Tool Lovers, I am very pleased to announce the first official release of FLAC, the Free Lossless Audio Codec, in over 6 years. FLAC is not dead! It is however a mature software product that is now being maintained by a team working under the auscpices of the Xiph.Org Foundation. The executive summary of changes in this new version: * Nothing major. * Source tree is now hosted in

Hi gluster: Im getting the cryptic 107 error, (I guess this means gluster can't see a peer)... gluster peer probe vm-2 peer probe: failed: Probe returned with unknown errno 107 When I can effectively ssh and ping a given server. I've seen other threads regarding this, some of them to deal with the "net.ipv4.ip_nonlocal_bind" parameter, and also a bug

Hello! For me it was best practice to disable "NetworkManager" on headless installations. Now suddenly I ran into an problem with several programs not starting correctly upon boot anymore. The problem seems to be that their unit files contain "After=network.target" but network.target wont wait till network is up and working, just waits for some low level network stuff.

I can run nmbd successfully, but smbd dies almost immediately when I run it, the smbd.log file has the message "bind failed on port 139 socket_addr = 0.0.0.0.". When I do a netstat -an | grep 139, it shows that tcp is listening on port 139. How do I resolve this conflict between tcp and smbd?

I'm running samba 4.1.2 on Linux Mint 15. Getting the following: ? ./samba-tool drs kcc samba-realm Failed to connect host 192.168.231.132 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.231.132 (samba-realm) on port 135 - NT_STATUS_CONNECTION_REFUSED. I don't see samba or smbd listening on port 135. 53 and 137 are. e.g.: ? netstat -anp | grep samba | grep

The data set (called 'chemdata') has 6 columns (4 factors, 1 date, 1 numeric) and I need to create subsets for each of one of the factors ('stream'). This has worked flawlessly for all but two streams which were created yesterday. The command I use to create the subsets is like this: > rnchH <- subset(chemdata, stream == 'RanchSpgsH', select = c(site, sampdate,

On 11/06/19 13:29, Rowland penny via samba wrote: > On 11/06/2019 13:13, Sebastian Arcus via samba wrote: >> >> On 11/06/19 11:49, Rowland penny via samba wrote: >>> On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >>>> >>>> On 11/06/19 11:07, Rowland penny via samba wrote: >>>>> On 11/06/2019 10:34, Sebastian Arcus via samba

--- .gnulib | 2 +- perl/lib/Sys/Guestfs/Lib.pm | 10 ++++++++-- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/.gnulib b/.gnulib index e2843e3..6d28070 160000 --- a/.gnulib +++ b/.gnulib @@ -1 +1 @@ -Subproject commit e2843e30e8c2885eb8cbc77e20c4e0f4d562d44d +Subproject commit 6d28070c3cc7a02107bf66402983b9fe4c6f8f6f diff --git

Hello All, First I would like to thank you all for for providing such a wonderful forum for Samba discussion. I have learned *vast* amounts perusing this list. I also would like to thank people for their replies to my previous question (Re: lock files on write protected shares). That all works great now! My most irritating problem recently has become worse as more people are using the

On 02/12/19 15:44, Rowland penny via samba wrote: > On 02/12/2019 15:32, Sebastian Arcus via samba wrote: >> >> On 02/12/19 15:10, Rowland penny via samba wrote: >> >> Thank you for the quick reply. I should have mentioned that these DC's >> are at at different sites. At each site there is only one Linux server >> - hence why the DC is also the file

On 02/12/19 16:53, Rowland penny via samba wrote: > On 02/12/2019 16:24, Sebastian Arcus via samba wrote: >> </snip> > >>> You should have 'vfs objects = dfs_samba4 acl_xattr recycle' >> >> Thank you very much for this - now it is working. This lack of >> permissions inheritance issue has been plaguing me for months - it is >> very

On 21/08/17 13:39, Robert Wolf wrote: > > On Mon, 21 Aug 2017, Sebastian Arcus wrote: > >> >> On 21/08/17 10:37, Gedalya wrote: >>> On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >>>> is there a 'preferred way'? should I tell users to use 143 over 993 ? or >>>> 993 over 143? or? >>> There is no concrete answer. There

On 11/06/19 11:49, Rowland penny via samba wrote: > On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >> >> On 11/06/19 11:07, Rowland penny via samba wrote: >>> On 11/06/2019 10:34, Sebastian Arcus via samba wrote: >>>> I've just upgraded a Samba AD server to 4.10.2 a few weeks ago from >>>> 4.x (I'm afraid I'm not sure the exact

Hy everybody, I have a little problem. Since a crash of my server we have problems to connect over the RSAT tools to our Samba 4 domain with the DNS tool. At the moment we have a Centos 6.5 server with Version 4.1.6-SerNet-RedHat-7.el6. If I connect to the AD server with the RSAT tool, i get this message in the log.smb: dnsserver: Found DNS zone _msdcs.nagy-blumen.at [2014/03/17

I've just bought an OpenVOX B200p ISDN card - and if I remember correctly from last time I used one of these - it is possible to use either DAHDI or mISDN with it. Are there any factors to consider when choosing which software to use? Is one better than the other - or does one have features which are not present in the other? I will be using it for a simple PBX, with 2 ISDN channels as

Hi, I have already tried to change for bindaddr=0.0.0.0 but it didn't worked. 2016-08-26 11:44 GMT-03:00, Frank Vanoni <mailinglist at linuxista.com>: > On Fri, 2016-08-26 at 10:12 -0300, Vitor Mazuco wrote: > >> bindaddr = all > > Try: > > bindaddr=0.0.0.0 > > > > > -- > _____________________________________________________________________

I am moving a Samba AD DC to a new server (I am merging two different hardware servers serving different functions). The new server has the same name as the old one, and same IP addresses on the network interfaces. I have moved the following directories: /var/lib/samba /var/cache/samba /etc/samba/ /var/named/ Samba will start, Bind starts (I'm using the Bind backend), the dns tests from

Hello! Thanks. I'm trying but still unsuccessful ..... Regards Em 30-05-2017 16:05, Sebastian Arcus via samba escreveu: > > On 30/05/17 15:42, Carlos A. P. Cunha via samba wrote: >> Hello! >> >> My Configuration: >> >> lsb_release -a >> >> No LSB modules are available. >> Distributor ID: Ubuntu >> Description: Ubuntu 14.04.3

Hello everybody! Currently, dovecot just kills itself if it detects that time has moved backwards more than a hardcoded number of seconds. I accept the reasons, but I do not like to restart dovecot manually after waiting for time to move forward again. A cron job would not help, because time might still be wrong when it restarts dovecot. All our systems run ntpd, but they might be offline