| 1 |
On Sun, Apr 19, 2015 at 6:18 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> On 04/18/2015 05:33 PM, Fernando Rodriguez wrote: |
| 3 |
>> On Saturday, April 18, 2015 3:59:15 PM walt wrote: |
| 4 |
>>> |
| 5 |
>>> execve("/bin/mount", ["mount"], [/* 61 vars */]) = 0 |
| 6 |
>>> |
| 7 |
>>> That number 61 on the 'bad' machine is 48, though, and I don't know where |
| 8 |
>>> that odd-looking string of characters is generated or what it means. To me |
| 9 |
>>> it looks like a comment in a file of 'c' code. |
| 10 |
>>> |
| 11 |
>>> Still stumped :( |
| 12 |
>> |
| 13 |
>> That would be the number of environment variables passed to execve. strace is |
| 14 |
>> just trying not to be too noisy. |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> Are there any differences in the options used in fstab between both machines, |
| 18 |
>> Especially the auto or noauto options or if one of them is using labels. The |
| 19 |
>> mount(8) man page may have more hints. |
| 20 |
> |
| 21 |
> As a quick-and-dirty way of testing your idea I moved /etc/fstab out of the way. |
| 22 |
> |
| 23 |
> I was surprised to learn that "mount" doesn't care about fstab, and doesn't even |
| 24 |
> bother to look for it (when invoked with no arguments). |
| 25 |
> |
| 26 |
|
| 27 |
It reads information from /etc/mtab primarily, as well as |
| 28 |
/run/mount/utab. Also, if /etc/mtab is a symlink, it reads from |
| 29 |
/proc/self/mountinfo instead of /etc/mtab. |
| 30 |
|
| 31 |
It seems like there is probably some difference in the data it is |
| 32 |
reading from those files on your system. Maybe post them so we can all |
| 33 |
have a look? |
Archives