Jump to content

fercho

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by fercho

  1. Here's what I have done to add read/write capabilities to my NTFS drive:

     

    $ sudo /etc/fstab

    /dev/sda5 / ext3 noatime 1 1

    /dev/sda7 /home ext3 noatime 1 2

    /dev/cdrom /media/cdrom auto umask=0022,users,iocharset=utf8,noauto,ro,exec 0 0

    /dev/sda1 /mnt/windows ntfs-3g rw,nls=utf8,umask=0222,uid=myuser,gid=myuser 0 0

    none /proc proc defaults 0 0

    /dev/sda6 swap swap defaults 0 0

     

    where myuser is my actual Linux user name. That will restrict any other user to read-only access (umask=0222) but will give myuser ownership of the files in the mounted partition.

     

    Regards,

  2. It turns out this is well hidden, but I think I have nailed it (but cannot check).

     

    The file /usr/share/msec/security.sh governs the daily security check (there is another file for the hourly check). I think the area to modify starts at line 74:

    ...

    I suggest you add |cifs to line 77 (inside the quotes) and test again; if it still fails then ensure your share is mounted in /mnt and try again. If it still fails then I am wrong.

    That was it! Thanks a lot pindakoe.

     

    Now, being CIFS the prefered way to access a samba resource, I think this fix should be added to the distro. Who should I contact about that?

  3. You may try an alternative samba mounting method, like smbnetfs (which is pretty much a standard currently).

    I thought that using cifs was the most current method of connecting to a samba share. Am I wrong?

    Thing is that performance is not great.. Same machine, same network, Windows XP is way faster accessing the samba machines...

     

    Any pointers on how to improve performace?

     

    Fer

  4. You should exclude that mount from msec security checking -- it doesn't make sense to that (unless you use that as a source of programs, but even then I guess that the administrator of that share will do the security checking).

    How would you go about that? What I did was to go to the GUI and added rules to give complete permissions to those files.

    I'm pretty sure that it would be more efficient to edit a configuration file for msec, but I do not know what should I be looking for... :unsure:

     

    Fercho

  5. Have a look in the file it will have all the files listed in your system which are in its idea the wrong permission.

     

    Some are probably world readable. If you dont want that change them and the file will be alot smaller

    Thanks michaelcole.

     

    I have found that most of the files listed in the log are located in a samba (cifs) mount. I can not change the permissions for those files! Maybe it is the cifs comand I'm using? I need to be able to edit files in those mount so I mount them using a line in fstab like this:

     

    //server/mount_point /home/feramos/mounted cifs uid=myuser,credentials=/etc/samba/ccorp,rw,domain=mydomain,setuids 0 0

     

    Suggestions ?

     

    Fercho

  6. So, I just got a notice from KDE complaining about my / partition to be 100% full.

    After some digging I found that one of the main culprits was this file /var/log/security/sgid.today:

     

    /var/log/security:

    total 3676305

    -rw-r----- 1 root root 2011881472 Dec 6 20:52 sgid.today

    -rw-r----- 1 root root 1098309632 Dec 7 10:00 unowned_user.today

     

    I do not see any entry on logrotate to deal with this file.. I do not have a clue on what process is using it or how can I shrink it..

    simply use vi to delete entries manually? :wall:

     

    I'm using Mandriva 2007.1 if that makes any difference...

     

    Some help will be appreciated.

     

    Fercho

×
×
  • Create New...