similar to: mount windows xp share

Hello Samba experts, I have a simple problem: i tried to use according to ch06_03.html manual page, directive revalidate in smb.conf config file. In smb.conf, i use directive security = share, but for a particular share (grant aces with user and pass) i want to use revalidate = yes option. The problem is that this feature is not working! 1. i used testparm to check the smb.conf file, and it

On (Wed) 01 Jul 2020 [22:09:50], Rikard Falkeborn wrote: > The id_table and feature_table pointers in struct virtio_driver are > pointers to const. Mark the corresponding static variables const to > allow the compiler to put them in read-only memory. > > Before: > text data bss dec hex filename > 25447 713 76 26236 667c

Hi! I use standard Bering 2.2.2. I am trying to get my FTP-server to work with another portnumber than 21 (On port 21 all works great, but I´m really interested in running two FTP-servers, so I want to figure this one out first). Read the FAQ: http://www.shorewall.net/FTP.html and now I got this setup: In Rules: DNAT net loc:192.168.3.2 tcp 99 In Shorewalls modules.conf (tried

Hi all, I?ve ran into a problem regarding D-channels. I have setup Asterisk (CVS-HEAD-03/21/05-16:41:57) on RH Fedora Core 3(2.6.10-1.770_FC3) I also have a digium wcte11xp card for connetivity to the PSTN(E1). When I start zttool i see that Current Alarms changes between Recovering and Blue Alarm/Recovering. I started to see these problems after i moved the digiumcard from one PCI slot to

If I have a resource called ''assets'' then I get for free a bunch of helpers, like assets_path new_asset_path and so forth, right? I would like to be able to create a call to one of these on the fly when I only find out the name of the resource at run time. For example I would like to do this: resource_name = "assets" resource_path(resource_name, method => :new)

Im having an issue that seems to only happen when trying to use a transaction. Ive used transactions many times in the past and Im at a loss as to why im getting the stack level too deep problem. SystemStackError - stack level too deep: actionpack (3.2.13) lib/action_dispatch/middleware/reloader.rb:70:in `'' I have a StackOveflow with more detail -

Virtio-mem managed memory is always detected and added by the virtio-mem driver, never using something like the firmware-provided memory map. This is the case after an ordinary system reboot, and has to be guaranteed after kexec. Especially, virtio-mem added memory resources can contain inaccessible parts ("unblocked memory blocks"), blindly forwarding them to a kexec kernel is

Virtio-mem managed memory is always detected and added by the virtio-mem driver, never using something like the firmware-provided memory map. This is the case after an ordinary system reboot, and has to be guaranteed after kexec. Especially, virtio-mem added memory resources can contain inaccessible parts ("unblocked memory blocks"), blindly forwarding them to a kexec kernel is

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

>> Now, let's clarify what I want regarding virtio-mem: >> >> 1. kexec should not add virtio-mem memory to the initial firmware >> memmap. The driver has to be in charge as discussed. >> 2. kexec should not place kexec images onto virtio-mem memory. That >> would end badly. >> 3. kexec should still dump virtio-mem memory via kdump. > > Ok,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After upgrading the kernel on an Asterisk box, asterisk segfaults on startup. It seems like it's the g729 codec that causes this: #0 0x4015acad in memset () from /lib/libc.so.6 #1 0x4022686a in load_module () at codec_g729b.c:416 #2 0x08054794 in ast_load_resource (resource_name=0x80d1068 "codec_g729b.so") at loader.c:298 #3

Hello, I have a compaq machine with compaq smart array raid and with 3com 905C 10/100 TXM network card (supporting PXE). I have setup an dhcp and tftp server for serving pxelinux.0 , memdisk and my dos images along with linux images (vmlinuz, initrd). Booting with vmlinuz and initrd is working fine on any machine but when I'm booting with memdisk along with dos image the result is: 1706:

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches

Hi all CentOS users, I have writing shell script for check oracle processes in real time and alert with e-mail. I read script like below NUMBEROFPRO=/oracle/10.2.0/db_1/bin/sqlplus / as sysdba <<EOF1 |grep processes|awk '{print $2}' SELECT resource_name,current_utilization,limit_value FROM V\$RESOURCE_LIMIT WHERE RESOURCE_NAME IN ('processes','sessions'); quit EOF1

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

hi just after talking to Jeremy, I downloaded the source he's using and compiled. core dump! This was without gatekeeper: (gdb) bt #0 0x40141118 in mallopt () from /lib/libc.so.6 #1 0x401400fc in malloc () from /lib/libc.so.6 #2 0x405e981b in PAbstractArray::SetSize(int) () from /usr/src/pwlib/lib/libpt_linux_x86_r.so.1 #3 0x405ed006 in PString::SetSize(int) () from

Hi all, In curl (the command line program), I can successfully log a user in using devise: def create respond_to do |format| format.json { if user_signed_in? return render :json => {:success => true, :errors => ["Already logged in."]} end resource = warden.authenticate!(:scope => resource_name, :recall =>

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where