Thanks for your help!
Since the whole root is over NFS, it is not possible that the FS is
mounted as nodev, otherwise the device files inside /dev wouldn't
work.
But I created a mount point to hold screen fifos, and it worked flawlessly.
It never occurred to me to try that, it was the simplest possible
solution knowing the problem must had been in the change to NFS.
Regards
2013/5/13, Alvaro Martínez <alvaro....@gmail.com>:
> Thanks for your help!
> Since the whole root is over NFS, it is not possible that the FS is mounted
> as nodev, otherwise the device files inside /dev wouldn't work.
> But I created a mount point to hold screen fifos, and it worked flawlessly.
> It never occurred to me to try that, it was the simplest possible solution
> knowing the problem must had been in the change to NFS.
>
>
> Regards
>
>
> 2013/5/13 James Cloos <cl...@jhcloos.com>
>
>> >>>>> "AM" == Alvaro Martínez <alvaro....@gmail.com> writes:
>>
>> AM> Every time I try to start screen, I receive the error
>> AM> "open fifo /home/alvaro/.screen/698.pts-1.slackberry: No such device
>> or
>> AM> address"
>>
>> What does:
>>
>> :; mount | grep ' / '
>>
>> report?
>>
>> It is possible that it is mounted with something like nodev.
>>
>> Does the /home/alvaro/.screen directory exist?
>>
>> To avoid the issue entirely, you could mount a tmpfs or ramfs at
>> ${HOME}/.screen to keep the fifo local. As a side benefit you won't
>> have any stale fifos to clean up after any crashes. :-/
>>
>> Or specify a different home for screen files, under a local filesystem.
>>
>> -JimC
>> --
>> James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
>>
>
_______________________________________________
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users
