search for: file_writ

That's just what I'm using, John. But I'm getting (eg) [Nov 4 21:46:16] ERROR[1676][C-00000003]: func_env.c:449 file2format: Cannot open '/home/logs/anonymous.txt': No such file or directory [Nov 4 21:46:16] ERROR[1676][C-00000003]: func_env.c:949 file_write: File '/home/logs/anonymous.txt' not in line format Asterisk is running as root (yeah, I know!), and has permissions on that directory. Hmmm.... On 4 November 2016 at 21:50, John Kiniston <johnkiniston at gmail.com> wrote: > I'm able to use the FILE function to create files...

I am trying to configure a system where I have two different NFS shares which point to the same directory. The idea is if you come in via one path, you will have read-only access and can''t delete any files, if you come in the 2nd path, then you will have read/write access. For example, create the read/write nfs share: zfs create tank/snapshots zfs set sharenfs=on tank/snapshots root

...0 +sambaLogoffTime: 2147483647 +sambakickoffTime: 2147483647 +sambaPwdCanChange: 0 +sambaPwdMustChange: 2147483647 +sambaacctFlags: [W ] +sambaLMPassword: $lmpassword +sambaNTpassword: $ntpassword +sambaSID: $SID-$sambaSID +sambaPrimaryGroupSID: $SID-0 "; @@ -516,8 +526,8 @@ sub file_write { my ($filename, $filecontent) = @_; local *FILE; - open (FILE, "> $filename") || - die "Cannot open -- ---------------------------------- ALEJANDRO SOLER e-mail: asoler@martinaditrento.com Administrador de Sistemas Martina di Trento S.A. Buenos Aires - Argentina Te...

...0 +sambaLogoffTime: 2147483647 +sambakickoffTime: 2147483647 +sambaPwdCanChange: 0 +sambaPwdMustChange: 2147483647 +sambaacctFlags: [W ] +sambaLMPassword: $lmpassword +sambaNTpassword: $ntpassword +sambaSID: $SID-$sambaSID +sambaPrimaryGroupSID: $SID-0 "; @@ -516,8 +526,8 @@ sub file_write { my ($filename, $filecontent) = @_; local *FILE; - open (FILE, "> $filename") || - die "Cannot open ?$filename? for writing: $!\n"; + open (FILE, ">".$filename) || + die "Cannot open $filename for writing: $!\n"; print FILE $fileconte...

Seems I can write to an existing file, but is there really no way of creating a new file to log some data to, without reverting to AGI? (will be different for each caller ID)

Hi everyone, The Linux Coda drivers and the ext3 patches don't seem to get along very well, at least in Linux 2.4.7. I've got a stock 2.4.7 kernel with a patch applied to the USB drivers (for a sony digital camera; see http://www.sujal.net/tech/linux/ just a change in unusual_devs.h). After I applied the ext3 patches from http://www.uow.edu.au/~andrewm/linux/ext3/ . Basically,

...it on the client is not. There are some other unneeded system calls: - One example is that show_progress() calls gettimeofday() even if do_progress is not set. show_progress() is called on every block, so there is an extra system call per (700 byte) block. - Another example is that file_write writes each matching (700 byte) block without buffering, so that's another system call per block. To study this behavior I used rsync-2.5.6cvs and had a benchmark area comprising around 7800 files of total size 530MB. Here are some results doing sends and receives via rsyncd, all on the...

These changes are based on Jason's latest hmm branch. Patch 1 was previously posted here [1] but was dropped from the orginal series. Hopefully, the tests will reduce concerns about edge conditions. I'm sure more tests could be usefully added but I thought this was a good starting point. [1] https://lore.kernel.org/linux-mm/20190726005650.2566-6-rcampbell at nvidia.com/ Ralph Campbell

This series adds new functions to the mmu interval notifier API to allow device drivers with MMUs to dynamically mirror a process' page tables based on device faults and invalidation callbacks. The Nouveau driver is updated to use the extended API and a set of stand alone self tests is added to help validate and maintain correctness. The patches are based on linux-5.5.0-rc6 and are for