search for: filessytem

Hi, I'm using rsync to backup a Linux Mandrake 10.1 (kernel 2.6.10) ext3 filesystem (+- 5GB of content, lots of little files) to a CIFS filesystem mounted with samba 3.0.10. The exact invocation of rsync is: /usr/local/bin/rsync -v -a --copy-links --delete /var/www /mnt/backup/backup_www Using the system provided rsync 2.6.3 and a self-compiled 2.6.5 this process runs for a while and then

When somebody is hammering on the system, I want to be able to detect who''s doing it, and hopefully even what they''re doing. I can''t seem to find any way to do that. Any suggestions? Everything I can find ... iostat, nfsstat, etc ... AFAIK, just show me performance statistics and so forth. I''m looking for something more granular. Either *who* the

Am 24.05.2017 um 17:50 schrieb Jeremy Allison via samba: > Here are some mitigation techniques from Red Hat in > case servers cannot be patched immediately: > 2. Mount the filessytem which is used by samba for its writeable share, > using "noexec" option. I would have expected this to be standard security precaution on all pure file servers (which is probably the most common use of Samba). Should the Samba-Wiki tell so, or shouldn't all Linux admins be sane...

Release Announcements --------------------- These are a security releases in order to address the following defect: o CVE-2017-7494 (Remote code execution from a writable share) ======= Details ======= o CVE-2017-7494: All versions of Samba from 3.5.0 onwards are vulnerable to a remote code execution vulnerability, allowing a malicious client to upload a shared library to a writable

Release Announcements --------------------- These are a security releases in order to address the following defect: o CVE-2017-7494 (Remote code execution from a writable share) ======= Details ======= o CVE-2017-7494: All versions of Samba from 3.5.0 onwards are vulnerable to a remote code execution vulnerability, allowing a malicious client to upload a shared library to a writable

...# group: root user::rwx group::rwx other::rwx [root at localhost /]# mv /var/named/backup.tgz ~ mv: cannot open `/var/named/backup.tgz' for reading: Permission denied [root at localhost /]# mount <redact> No readonly mounts </redact> [root at localhost /]# df -h <redact> Each filessytem has plenty of free space </redact> [root at localhost /]# dir /var/named/ total 72 drwxr-x--- 6 root named 4096 Nov 11 11:32 . drwxr-xr-x 24 root root 4096 Apr 1 2010 .. -rwxrwxrwx 1 root root 6651 Nov 11 11:32 backup.tgz drwxr-x--- 6 root named 4096 Nov 11 11:48 chroot drwxrwx...

This should be simple, but it's not, unless I'm forgetting something. Writing a script, an arg is a filename. So fname=$1 But I want that expanded to include the full path and filename, not just what is given as the arg on the command line. E.g., if the user's cwd is /home/joe/a/b/c/ and he specifies ../x/file-a.ext then the function/utility should transform that into the

...nt/data.bin bs=1GB count=1 Without this patch, the ''dd'' command would succeed in writing 1 GB of data even though the underlying disk in Dom0 was only 200 MB in size. More complex tests of copying a whole directory heirarchy across resulted in catastrophic data corruption of the filessytem itself. Manual fsck was needed to fixup the filesystem & there were many very bad errors needing fixing. With this patch applied the DomU sees the I/O failures and kernel logs messages Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 722127 Dec 1 11:02:53 dhcp-5-...

...or, as you say, it might be the culprit; we don't know yet). Some possible suggestions: 0_ Check whether there is a BIOS (firmware) update available for your hardware. 1_ Wipe the first few MBs of your SD-Card, (warning: data will be erased!). 2_ Create a *new* MBR, partition table, and FAT filessytem. 3_ Use (and post here) an adequate, complete syslinux.cfg (especially if it works with 4.06). 4_ Use official prebuilt binaries downloaded from kernel.org. 5_ Test on another hardware combination (different mainboard / USB port / USB cable / USB boot device...). 6_ Please also test in an adequat...

...I did find a cool functionality called locate and updatedb Updatedb creates the database of your files, locate does superfast searches. It essentially does a superfast "find" on your root filesystem, giving you the fully qualified path of all hits. You can create db's on your other filessytems. The problem is that it can get stale, but you can update it before doing your searches. Plus it gives you a fully qualified path name with the results. So if you need to do a set of searches on a filesystem (or whole system) run updatedb on each target filesystem to create the db for that fi...

...redhat.com/show_bug.cgi?id=1450347#c3 Huzaifa S. Sidhpurwala 2017-05-15 04:02:57 EDT Mitigation: Any of the following: 1. SELinux is enabled by default and our default policy prevents loading of modules from outside of samba's module directories and therefore blocks the exploit 2. Mount the filessytem which is used by samba for its writeable share, using "noexec" option. 3. Add the parameter: nt pipe support = no to the [global] section of your smb.conf and restart smbd. This prevents clients from accessing any named pipe endpoints. Note this can disable some expected functi...

Hi I have tried to install syslinux 4.06 on the SD card again, it works like a charm. I am being very carefull with c32 files from the same version bootloader. No success. I am also unmounting /dev/sdb1 before installing syslinux, as mentioned in the given documentations. In the pasted syslinux.cfg content--- I have also tried using only one DEFAULT directive. No success. syslinux boots

...culprit; we don't know yet). > > Some possible suggestions: > 0_ Check whether there is a BIOS (firmware) update available for your > hardware. > 1_ Wipe the first few MBs of your SD-Card, (warning: data will be > erased!). > 2_ Create a *new* MBR, partition table, and FAT filessytem. > 3_ Use (and post here) an adequate, complete syslinux.cfg (especially > if it works with 4.06). > 4_ Use official prebuilt binaries downloaded from kernel.org. > 5_ Test on another hardware combination (different mainboard / USB port > / USB cable / USB boot device...). > 6_ Pl...