similar to: 6402576 Sometimes port_getn() never returns indicating that a socket has become writable

Author: praks Repository: /hg/zfs-crypto/gate Revision: 4c3b7ab574cc73502effa96c11c293e04fd54309 Log message: 6256083 Need a lightweight file page mapping mechanism to substitute segmap 6387639 segkpm segment set to incorrect size for amd64 Files: create: usr/src/uts/common/vm/vpm.c create: usr/src/uts/common/vm/vpm.h update: usr/src/pkgdefs/SUNWhea/prototype_com update:

Environment: OpenBSD v 3.6 Release, Samba ver.: Samba 3.0.5 LAN: 192.168.0.0/24, Samba servers: 2 installed replacing workgroup peer shares Windows version: XP Pro History: The 2 Sambas were installed last year and appear to have operated well until recently. Client admin now reports that, after some time connected to a shared directory, searching for files results in a Win error message to the

Normally, if the tinc server’s MTU discovery response can reach the tinc client side, they always can negotiate with a certain MTU size, but the case is, sometimes, the client sent variety size of MTU probe packet to server, but the server never respond. Sometimes, if I change the client side’s tinc port, the server’s MTU response can received by client. BTW, the above case are all regarding

Author: Darren Moffat <darrenm at opensolaris.org> Repository: /hg/zfs-crypto/gate Latest revision: 9bb308a0778101fcef9ff65336bcec8e68a7bd06 Total changesets: 40 Log message: resynv onnv-gate Files: .hgtags deleted_files/usr/src/cmd/fps/Makefile.inc deleted_files/usr/src/cmd/fps/Makefile.subdirs deleted_files/usr/src/common/crypto/aes/aes_cbc_crypt.c

Greetings, thanks to all of you who work on Dovecot! I have prepared a small patch to support Solaris 10 and Opensolaris' event port mechanism for both the ioloop and the notify subsystems. It seems to work fine for me, but I haven't conducted any extensive testing. It would be great if someone could review and/or test it (and if it could eventually enter the code base). I have

I recently made a Live USB by using the directions in the LiveCD Trac. It works very well, but I was wondering if there is a way the partition - in my case, /dev/sda1, can be made writable. I tried changing the kickstart file to mount everything RW, but it did not work. I know I can always create a second partition on the pendrive, but I would like all filesystems accessible by both CentOS and

Hi, I am trying to install OTRS on centos 4.4. I keep getting Warning: Kernel/Config.pm isn't writable! when i try to run the installer. I have done chmod 777 on the Config.pm file etc but still it will not work. I also did "chown Config.pm apache" and that did not work either. Please can someone help me. This looks like a simple issue which i cannot able to solve. below is

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

Hello all I'm suggesting to add line 'writable = yes' for Profiles share in file examples/smb.conf.default. Then the complete share def looked like ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = yes ; writable = yes The reason is simply I spent two days figuring out why my Samba PDC did not work. That line was missing. Not very clever, I

In xen 3.0.4-1 source, where is the *unhook/rehook page table implementation* which is important things in ''writable page table mode''.? I can''t find it. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hello, i'm running samba 2.2.2 on Linux 2.4.10. i have 3 other pc's on the network, all running win98. so there is LINUX, WIN1, WIN2 and WIN3. the problem is that some of my shares are not writeable, but they read perfectly, both locally using smbclient, as well as from all the win98 clients. i noticed that all of the problematic shares are mounted from FAT partitions on LINUX, which

Not too sure what this is about but it is repeatable : On Solaris 8 ( either Sparc or x86 ) after the config stage I get : Text relocation remains referenced against symbol offset in file <unknown> 0x0 lib/ldb/common/ldb_modules.o ld: fatal: relocations remain against allocatable but non-writable sections any thoughts ? The configuration is fine .. same as with samba 3.0.31 actually and

Fellows, I've had this stagging for too long: For some writable (RW) variables, that support ranges of values, ENUM and STRING are too limited and not adapted. So it's worth adding a new RANGE type, with the needed driver function (dstate_addrange()) and server / client support. Thus, I'm intending to do the following network protocol addition: * new RANGE type, for the "GET

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

Hi, I have a new CentOS sever install. I've also installed suPHP to replicate a live server. When I upload file via FTP the permissions seem OK, however the directories copied are not writable?? Any ideas? I have tried chmod 777 and that's not working either. Could is be a suPHP issue? I have 'suPHP_UserGroup GROUP USER' setup in my virtual directory and the user is also in the

I'm curious. Why are so many system-generated files world-writable? On my Mandriva laptop, every day I get warnings that world-writable files are found in /tmp, /far/lib/ /var/run/ and /var/spool, and every day msec reports that it has changed the mode of several files in /var/log/. Why are they created like that? Anne -------------- next part -------------- A non-text attachment was

Hi all, I was wondering if it possible to have a Centos LiveCD installation boot from a Compact Flash in a embeded x86 (Wrap/Alix) platform *and* be able to save the changes made to the File System back to the Flash memory. So, the next time the LiveCD boots it will have all the changes made. The problem I'm trying yo solve is: - fast boot time - fast recovery when the Linux is shutdown

I can also confirm this, on my own mail server since upgrading to beta1. Dovecot always makes the base_dir world-writable on startup. ----- Forwarded message from Oleg Safiullin <form@pdp-11.org.ru> ----- Date: Fri, 20 Jan 2006 07:09:17 +0600 From: Oleg Safiullin <form@pdp-11.org.ru> To: brad@openbsd.org Subject: dovecot 1.0beta1 Hi. After update dovecot to 1.0beta1 some strange

Hi, first of all Thanks for any help. I would like to share with SAMBA a Unix path to Windows clients. The problem i have is this: I want that this share would be READONLY for someone (or somewhat TCP/IP address) and READABLE/WRITABLE for someone else (even if throught a user/passwd authentication). I'm using Samba 2.2.6 and Wnt/W2k clients. I'm trying to setup my environment fixing