bug#31184: tail -f on Network FS not refreshing as soon as the file is changed.

[Jewsco Pius Jacquez]

Padraig, thanks for your response,

The ---disable-inotify didn't refresh either.

address@hidden ~]# stat -f -c '%t %T'  /media/samba/test.file
ff534d42 cifs
address@hidden ~]# df -h /media/samba/test.file
Filesystem            Size  Used Avail Use% Mounted on
//10.124.61.52/finance
                       14G   13G  1.6G  89% /media/samba
address@hidden ~]# grep /media/samba /proc/mounts
//10.124.61.52/finance/ /media/samba cifs 
rw,relatime,sec=ntlm,cache=loose,unc=\134\13410.124.61.52\134finance,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.124.61.52,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,echo_interval=60,actimeo=1
 0 0
address@hidden ~]#


Thanks,
Jewsco


-----Original Message-----
From: Pádraig Brady [mailto:address@hidden 
Sent: Tuesday, April 17, 2018 2:29 AM
To: Jewsco Pius Jacquez <address@hidden>; address@hidden
Subject: Re: bug#31184: tail -f on Network FS not refreshing as soon as the 
file is changed.

On 16/04/18 10:11, Jewsco Pius Jacquez wrote:
> Hello,
> 
> We have a legacy application that is using tail -f command in the application 
> and is running in Redhat 9 under a shared Samba filesystem.
> 
> We want to migrate the application to RHEL7 and we noticed that the tail -f 
> command here is not refreshing as soon as the file get changed. In Redhat 9, 
> it is working fine, every write on the file got reflected straight away(no 
> waiting interval).
> 
> Is there a way that we can make the tail -f working as it was in Redhat 9? 
> For this reason, we are not able to migrate our Legacy application.

To get around the issue, the undocumented ---disable-inotify option may help 
(note the three dashes)

If that does help then there is an issue with the misdetection of a known file 
system as local, when it should be treated as remote.
Can you show the file system type for the file you're trying to tail, using:

  stat -f -c '%t %T' /path/to/your/file

cheers,
Pádraig
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>